#package_submissions

2016-12-13

Kasper D. Hansen (22:00:46): > @Kasper D. Hansen has joined the channel

Kasper D. Hansen (22:02:27): > added an integration to this channel: github

Kasper D. Hansen (22:02:44): > disabled an integration in this channel: github

2016-12-14

Marcel Ramos Pérez (11:56:27): > @Marcel Ramos Pérez has joined the channel

Marcel Ramos Pérez (11:57:54): > added an integration to this channel: github

Levi Waldron (12:26:32): > @Levi Waldron has joined the channel

Kasper D. Hansen (13:11:32): > Thanks Marcel

Nitesh Turaga (16:08:49): > @Nitesh Turaga has joined the channel

Sean Davis (16:20:25): > @Sean Davis has joined the channel

Unknown User (17:39:17): - Attachment: #215 VariantToolsData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/lawremi/VariantToolsData > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2016-12-15

Unknown User (10:31:23): - Attachment: #216 goSTAG > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/brianbennettphd/goSTAG > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:20:24): - Attachment: #217 IntEREst > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/gacatag/IntEREst > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2016-12-16

Unknown User (17:45:50): Unknown User (17:45:51):

2016-12-18

Unknown User (17:20:17): - Attachment: #218 branchpointer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/betsig/branchpointer > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:20:20): Unknown User (17:40:26): - Attachment: #219 branchpointer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/betsig/branchpointer > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2016-12-19

Unknown User (16:26:07): Unknown User (18:28:05): Unknown User (18:28:06):

2016-12-21

Unknown User (05:00:39): - Attachment: #220 PathparintGEOData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hidelab/pathprintGEOData.git > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (05:00:39): Unknown User (05:12:39): - Attachment: #221 pathprintGEOData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hidelab/pathprintGEOData.git > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (05:12:40): Unknown User (05:14:30): - Attachment: #222 pathprintGEOData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hidelab/pathprintGEOData > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2016-12-22

Unknown User (09:48:17): Unknown User (15:35:13): - Attachment: #223 mimager > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/aaronwolen/mimager > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2016-12-23

Unknown User (08:52:04): - Attachment: #224 MSPC– Bioconductor Package for Multiple Sample Peak Calling > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > MSPC– Bioconductor Package for Multiple Sample Peak Calling > > • Repository: Repository: https://github.com/julaiti/MSPC.git > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:52:06): Unknown User (09:01:08): - Attachment: #225 MSPC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/julaiti/MSPC > > Confirm the following by editing each check box to ‘[x]’ > > • ‘[x]’ I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • ‘[x]’ I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • ‘[x]’ I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • ‘[x]’ My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • ‘[x]’ I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • ‘[x]’ The ‘devel’ branch for new packages and features. > • ‘[x]’ The stable ‘release’ branch, made available every six > months, for bug fixes. > • ‘[x]’ Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:17:08): Unknown User (15:17:09):

2016-12-26

Unknown User (12:13:22): - Attachment: #226 RTNmotifs package submission > Dear Bioc Reviewers, > > Please, see below the GitHub repository URL for our new software called “RTNmotifs”. The software presented here is an original contribution that offers a bioinformatics approach to infer possible co-regulation between regulon pairs (which we call ‘dual regulons’). The tool represents the 1st level of our analysis pipeline dedicated to assess the complexity of co-regulation between different types of regulatory elements, and possible effects on regulatory network. > > Sincerely, > Vinicius, Clarice and Mauro > > • Repository: https://github.com/chagasVinicius/RTNmotifs > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2016-12-27

Unknown User (04:14:50): - Attachment: #227 MetCleaning > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jaspershen/MetCleaning > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2016-12-28

Unknown User (12:01:23): - Attachment: #228 TCGA Workflow: Analyze cancer genomics and epigenomics data using Bioconductor packages (workflow package) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/BioinformaticsFMRP/f1000_TCGA_Workflow > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:01:24): Unknown User (12:20:41): - Attachment: #229 TCGA Workflow: Analyze cancer genomics and epigenomics data using Bioconductor packages (workflow package) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/BioinformaticsFMRP/f1000_TCGA_Workflow > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-01-02

Unknown User (21:52:38): - Attachment: #230 BioMedR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (21:52:39): Unknown User (21:59:42): - Attachment: #231 BioMedR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wind22zhu/BioMedR > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-01-03

Unknown User (07:56:19): - Attachment: #232 BioMedR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wind22zhu/BioMedR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > -[x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (07:56:20):

2017-01-04

Unknown User (12:50:03): - Attachment: #233 IntramiRExploreR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/sbhattacharya3/IntramiRExploreR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:29:09): - Attachment: #234 AHCytoBands > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/lawremi/AHCytoBands > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (21:31:54): - Attachment: #235 BioMedR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wind22zhu/BioMedR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (21:31:54):

2017-01-05

Unknown User (17:57:12): Unknown User (18:11:27): Unknown User (18:11:27): Unknown User (18:11:28): Unknown User (18:11:28):

2017-01-06

Unknown User (04:07:25): - Attachment: #236 BioMedR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (04:07:26): Unknown User (04:09:34): - Attachment: #237 BioMedR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wind22zhu/BioMedR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (04:09:35): Unknown User (04:35:38): Unknown User (04:37:02): - Attachment: #238 BioMedR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wind22zhu/BioMedR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (04:37:02):

2017-01-09

Unknown User (15:46:33): - Attachment: #239 RIVERpkg > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ipw012/RIVERpkg > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-01-10

Unknown User (23:09:48): - Attachment: #240 PPInfer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/PPInfer > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (23:09:49): Unknown User (23:13:38): - Attachment: #241 PPInfer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/dongminjung/PPInfer > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-01-11

Unknown User (03:01:02): Unknown User (10:53:39): - Attachment: #242 MIGSA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jcrodriguez1989/MIGSA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-01-12

Unknown User (08:54:49): Unknown User (10:57:23): - Attachment: #243 RTNduals > Dear Valerie (@vobencha), > > Please find attached our revised package now renamed to RTNduals. I hope you will be able to continue the review process of our package, for which you have provided relevant suggestions.
> > The link to the old issue is: https://github.com/Bioconductor/Contributions/issues/226#issuecomment-269227969 > > Please let us know any questions. > > Sincerely, > Vinicius, Clarice and Mauro > > • Repository: https://github.com/chagasVinicius/RTNduals > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:57:24): Unknown User (11:00:30): - Attachment: #244 RTNduals > Dear Valerie (@vobencha), > > Please find attached our revised package now renamed to RTNduals. I hope you will be able to continue the review process of our package, for which you have provided relevant suggestions. > > Please let us know any questions. > > Sincerely, > Vinicius, Clarice and Mauro > > • Repository: https://github.com/chagasVinicius/RTNduals > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:40:38): Unknown User (11:40:38): Unknown User (11:40:38): Unknown User (11:40:38): Unknown User (11:40:38): Unknown User (11:40:39):

2017-01-13

Unknown User (07:17:16): - Attachment: #245 epiNEM > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/cbg-ethz/epiNEM > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-01-14

Unknown User (11:43:44): - Attachment: #246 SPBTest3 – please ignore > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor/spbtest3 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:43:45): Unknown User (13:18:38):

2017-01-15

Unknown User (19:14:08): - Attachment: #247 AllSorts > • Repository: https://github.com/Oshlack/AllSorts > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-01-16

Unknown User (20:55:22): - Attachment: #248 BLMA: A package for bi-level meta-analysis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/nguyentin/BLMA > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > BLMA_0.99.0.tar.gz

Unknown User (20:55:23): Unknown User (21:29:10): - Attachment: #249 BLMA: A package for bi-level meta-analysis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/nguyentin/BLMA > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (21:29:11): Unknown User (21:34:44): - Attachment: #250 BLMA: A package for bi-level meta-analysis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/nguyentin/BLMA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-01-17

Unknown User (01:54:05): - Attachment: #251 biotmle > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/nhejazi/biotmle/pkg > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (01:54:06): Unknown User (01:58:43): - Attachment: #252 biotmle > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/nhejazi/biotmle/pkg/ > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (01:58:43): Unknown User (09:44:26): - Attachment: #253 sampleClassifierData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/khadija-a/sampleClassifierData > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:10:32): - Attachment: #254 biotmle > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/nhejazi/biotmle > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-01-18

Unknown User (20:21:26):

2017-01-20

Unknown User (12:53:52): - Attachment: #255 Submission of TSRchitect to Bioconductor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/BrendelGroup/TSRchitect > > Note: for formal testing, please clone the ‘Bioc’ branch of our github repository and install using the following commands. > > {eval=FALSE} > git clone [https://github.com/BrendelGroup/TSRchitect](https://github.com/BrendelGroup/TSRchitect) --branch Bioc --single-branch > R CMD build TSRchitect > > > The above information can be found in the file INSTALL.md. > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:53:52): Unknown User (12:57:59): - Attachment: #256 TSRchitect > Dear Bioconductor Team: > > We submit our package, TSRchitect, for inclusion in the Bioconductor package repository. > > • Repository: https://github.com/BrendelGroup/TSRchitect > > Note: for formal testing, please clone the ‘Bioc’ branch of our github repository and install using commands found in INSTALL.md > > Best regards, > > Taylor > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-01-22

Unknown User (12:08:45): - Attachment: #257 hicrep > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:08:45):

2017-01-23

Unknown User (05:22:55): - Attachment: #258 motifcounter > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wkopp/motifcounter > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:27:39): Unknown User (16:11:57): - Attachment: #259 hicrep > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/MonkeyLB/hicrep > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-01-24

Unknown User (18:10:30): Unknown User (18:10:31): Unknown User (18:10:31):

2017-01-26

Unknown User (04:32:00): - Attachment: #260 EventPointer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jpromeror/EventPointer > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (05:33:15): - Attachment: #261 twoddpcr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/CRUKMI-ComputationalBiology/twoddpcr > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (06:22:47): Unknown User (11:37:09): - Attachment: #262 Organism.dplyr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:37:22): Unknown User (11:41:24): Unknown User (11:43:54): - Attachment: #263 Organism.dplyr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor/Organism.dplyr > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-01-27

Unknown User (11:26:45): - Attachment: #264 methylInheritanceSim > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/belleau/methylInheritanceSim > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:32:23): - Attachment: #265 methylInheritance > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/adeschen/methylInheritance > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-01-28

Unknown User (08:54:57): Unknown User (08:54:57):

2017-01-30

Unknown User (12:54:28): - Attachment: #266 MaxContrastProjection > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/DragonDuck/MaxContrastProjection > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:29:33): - Attachment: #267 wiggleplotr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/kauralasoo/wiggleplotr > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-01-31

Unknown User (18:16:54): - Attachment: #268 hicrep > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/MonkeyLB/hicrep > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:16:55):

2017-02-01

Unknown User (21:19:21): - Attachment: #269 WebGestalt > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wangj26/WebGestalt > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-02-02

Unknown User (10:16:37): - Attachment: #270 imageanalysisBrain > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/mknoll/imageanalysisBrain > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-02-03

Unknown User (18:39:36):

2017-02-04

Unknown User (09:16:58): - Attachment: #271 AHEnsDbs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jotsetung/AHEnsDbs > • Note: this package provides metadata to include EnsDb SQLite files (for the ensembldb package) to AnnotationHub. If possible, I would request Valerie Obenchain as reviewer for the package. Thanks. > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-02-07

Unknown User (15:40:36): Unknown User (17:23:49):

2017-02-09

Unknown User (06:06:21): - Attachment: #272 DaMiRseq package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/BioinfoMonzino/DaMiRseq > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Kasper D. Hansen (10:14:21): > @Sean Davisperhaps another channel, although it is an interesting question (that I don’t really understand to be honest)

Sean Davis (10:15:06): > Thanks,@Kasper D. Hansen. Not meant to go to public.

2017-02-11

Unknown User (14:22:24): Unknown User (14:22:24): Unknown User (14:22:25):

2017-02-13

Unknown User (09:11:13): - Attachment: #273 MetCleaning > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:11:14): Unknown User (09:14:52): - Attachment: #274 MetCleaning > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jaspershen/MetCleaning > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:14:53): Unknown User (09:16:57): Unknown User (09:18:18): - Attachment: #275 MetCleaning > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jaspershen/MetCleaning > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:18:19): Unknown User (09:25:22):

2017-02-14

Unknown User (10:40:28):

2017-02-17

Unknown User (08:37:45): - Attachment: #276 MaxContrastProjection > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/DragonDuck/MaxContrastProjection > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:17:01): - Attachment: #277 GenomicDataCommons > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:17:02): Unknown User (16:18:58): - Attachment: #278 GenomicDataCommons > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor/GenomicDataCommons > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:42:57): Unknown User (17:42:57):

2017-02-19

Unknown User (18:41:20): - Attachment: #279 PathwaySplice > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/SCCC-BBC/PathwaySplice > > Confirm the following by editing each check box to ‘[x]’ > > • [ X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X ] The ‘devel’ branch for new packages and features. > • [ X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ X] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-02-20

Unknown User (02:19:39): - Attachment: #280 Transcriptome-guided quality assessment of methylated RNA immunoprecipitation sequencing data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/skyhorse/Trumpet > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (02:19:40):

2017-02-21

Unknown User (20:58:04): - Attachment: #281 Transcriptome-guided quality assessment of methylated RNA immunoprecipitation sequencing data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/“skyhorsetomoon/Trumpet > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (20:58:05):

2017-02-22

Unknown User (03:13:12): - Attachment: #282 Transcriptome-guided quality assessment of Methylated RNA immunoprecipitation sequencing data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/skyhorsetomoon/Trumpet > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (03:13:13): Unknown User (06:48:35): - Attachment: #283 Trumpet > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/skyhorsetomoon/Trumpet > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:33:28): - Attachment: #284 NADfinder > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:33:30): Unknown User (17:55:50): - Attachment: #285 NADfinder > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jianhong/NADfinder > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-02-23

Unknown User (03:14:24): - Attachment: #286 Trumpet > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/skyhorsetomoon/Trumpet > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (03:14:25): Unknown User (03:36:18): - Attachment: #287 Trumpet revise > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/skyhorsetomoon/Trumpet > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (03:36:19): Unknown User (03:48:21): - Attachment: #288 Trumpet3 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/skyhorsetomoon/Trumpet > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (03:48:21): Unknown User (04:27:27): - Attachment: #289 Trumpet > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/skyhorsetomoon/Trumpet > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (04:27:29):

2017-02-24

Unknown User (02:35:58): - Attachment: #290 Trumpet Revise2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/skyhorsetomoon/Trumpet > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (02:35:59):

2017-02-28

Unknown User (07:21:38): - Attachment: #291 Trumpet > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/skyhorsetomoon/Trumpet > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (07:21:39): Unknown User (11:36:03): - Attachment: #292 BiocFileCache > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor/BiocFileCache > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (21:58:09): - Attachment: #293 motifmatchr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/GreenleafLab/motifmatchr > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-03-01

Unknown User (03:41:28): Unknown User (03:41:28): Unknown User (03:41:28): Unknown User (03:41:28): Unknown User (23:19:17): - Attachment: #294 Trumpet2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/skyhorsetomoon/Trumpet2 > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (23:19:18):

2017-03-02

Unknown User (02:51:23): - Attachment: #295 Trumpet > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/skyhorsetomoon/Trumpet > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (02:51:24): Unknown User (06:42:59): Unknown User (10:15:40): - Attachment: #296 RITANdata > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/MTZimmer/RITANdata > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:15:41):

2017-03-03

Unknown User (12:04:32): - Attachment: #297 https://github.com/YosefLab/ImpulseDE2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:04:33): Unknown User (12:06:15): - Attachment: #298 https://github.com/YosefLab/ImpulseDE2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:06:17): Unknown User (12:07:53): - Attachment: #299 https://github.com/YosefLab/ImpulseDE2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:07:53): Unknown User (13:00:31): Unknown User (14:04:33): - Attachment: #300 RITANdata > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/MTZimmer/RITANdata > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:08:19): - Attachment: #301 multiOmicsViz > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wangj26/multiOmicsViz > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-03-04

Unknown User (04:42:17): Unknown User (04:42:17): Unknown User (04:42:17): Unknown User (04:42:18): Unknown User (04:48:12): - Attachment: #302 DASC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (04:48:12):

2017-03-05

Unknown User (15:43:02): - Attachment: #303 ImpulseDE2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/YosefLab/ImpulseDE2 > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (21:30:14): - Attachment: #304 DASC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (21:30:15): Unknown User (21:36:23): - Attachment: #305 DASC – New package for Batch Detection > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/aayushraman/DASC > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-03-06

Unknown User (09:01:47): - Attachment: #306 rexposome > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/isglobal-brge/rexposome > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-03-07

Unknown User (11:33:39): Unknown User (11:33:40):

2017-03-08

Unknown User (00:09:18): - Attachment: #307 decd: A tool for differential expression analysis and exploratory investigation to complex diseases using big data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/menggf/decd.git > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (00:09:19): Unknown User (00:25:30): - Attachment: #308 decd: A tool for differential expression analysis and exploratory investigation to complex diseases using big data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/menggf/decd.git > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (00:25:32): Unknown User (09:05:08): Unknown User (09:24:45): - Attachment: #309 semisup > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/rauschenberger/semisup > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:16:06): - Attachment: #310 IMAS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hangost/IMAS > Confirm the following by editing each check box to ‘[x]’ > • [ x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x ] The ‘devel’ branch for new packages and features. > • [ x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-03-09

Unknown User (01:56:47): - Attachment: #311 AnnotationFilter > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor/AnnotationFilter > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:23:02): - Attachment: #312 GA4GHclient > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/labbcb/GA4GHclient > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:10:05): - Attachment: #313 A R package for differential expression analysis and exploratory investigation to complex disease using big data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/menggf/decd.git > Confirm the following by editing each check box to ‘[x]’ > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:10:06): Unknown User (18:23:09): - Attachment: #314 A R package for differential expression analysis and exploratory investigation to complex disease using big data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/menggf/decd.git > Confirm the following by editing each check box to ‘[x]’ > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:23:10):

2017-03-10

Unknown User (02:27:35): - Attachment: #315 decd > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/menggf/decd > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:25:44): - Attachment: #316 picaplot:package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jinhyunju/picaplot > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (20:31:49): Unknown User (20:31:49): Unknown User (20:31:50):

2017-03-11

Unknown User (03:17:18): Unknown User (13:03:49): - Attachment: #317 netReg > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/dirmeier/netReg > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-03-13

Unknown User (04:32:28): - Attachment: #318 Submitting BioCor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/llrs/BioCor > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:45:37):

2017-03-14

Unknown User (08:36:51): - Attachment: #319 BioMedR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wind22zhu/BioMedR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:36:53): Unknown User (11:58:56): - Attachment: #320 AUCell > • Repository: https://github.com/aertslab/AUCell > > Confirm the following by editing each check box to ‘[x]’ > > • [ x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x ] The ‘devel’ branch for new packages and features. > • [ x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:18:52): - Attachment: #321 GENIE3 > • Repository: https://github.com/aertslab/GENIE3 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-03-15

Unknown User (19:17:08): Unknown User (20:00:35): Unknown User (20:00:35): Unknown User (20:00:35): Unknown User (20:00:35):

2017-03-16

Unknown User (00:30:40): - Attachment: #322 coexnet: An R package to build CO-EXpression NETworks from Microarray Data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/gibbslab/coexnet > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:10:32): Unknown User (13:10:36): Unknown User (17:34:52): - Attachment: #323 miRNAss > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/cyones/miRNAss > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-03-18

Unknown User (00:12:06): - Attachment: #324 GenomicScores > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/rcastelo/GenomicScores > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:30:31): - Attachment: #325 MICMIC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/tongyin9002/MICMIC.0.99.0 > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:30:32): Unknown User (11:36:55): - Attachment: #326 MICMIC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/tongyin9002/MICMIC.0.99.0 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:36:55): Unknown User (11:43:12): - Attachment: #327 MICMIC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/tongyin9002/MICMIC > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:43:44):

2017-03-19

Unknown User (10:24:31): - Attachment: #328 MICMIC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/tongyin9002/MICMIC > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:24:32): Unknown User (11:15:54):

2017-03-20

Unknown User (08:00:56): - Attachment: #329 cydar > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/MarioniLab/cydar > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-03-22

Unknown User (09:36:17): - Attachment: #330 ideal > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/federicomarini/ideal > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-03-24

Unknown User (11:01:05): - Attachment: #331 CATALYST: Cytometry dATa anALYSis Tools > • Repository: https://github.com/HelenaLC/CATALYST > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor [Package Submission][2] > instructions. My package is consistent with the Bioconductor > [Package Guidelines][1]. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the [support site][3] for issues that users may > have, subscribing to the [bioc-devel][4] mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using [Subversion][5] > (optionally [via GitHub][6]).

2017-03-27

Unknown User (04:07:35): Unknown User (04:07:35): Unknown User (04:07:35): Unknown User (04:07:35): Unknown User (04:07:36): Unknown User (18:09:44): - Attachment: #332 ATACqc > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jianhong/ATACqc > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-03-28

Unknown User (15:53:13): - Attachment: #333 basecallQC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository:https://github.com/ThomasCarroll/basecallQC > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:00:42): Unknown User (16:01:19): Unknown User (18:53:21):

2017-03-29

Unknown User (11:12:15): - Attachment: #334 D3GB > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/BioinfoUSAL/D3GB > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-03-30

Unknown User (10:21:20): - Attachment: #335 GA4GHshiny > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/labbcb/GA4GHshiny > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:22:15): - Attachment: #336 NOMAD > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/carlmurie/NOMAD > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-03-31

Unknown User (11:01:52): - Attachment: #337 omicRexposome > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/isglobal-brge/omicRexposome > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:50:01): Unknown User (15:01:46): Unknown User (15:01:47): Unknown User (15:01:47): Unknown User (15:01:47): Unknown User (15:01:47): Unknown User (15:01:47): Unknown User (16:00:03): - Attachment: #338 pgca > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/gcohenfr/pgca > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-04-01

Unknown User (00:25:12): - Attachment: #339 RaggedExperiment > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor/RaggedExperiment > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-04-03

Unknown User (06:37:03): - Attachment: #340 ndexr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/frankkramer-lab/ndexr > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:25:15): Unknown User (18:32:07): - Attachment: #341 TReNA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/PriceLab/TReNA > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (23:51:07): Unknown User (23:55:46):

2017-04-06

Unknown User (13:50:35): Unknown User (13:50:39):

2017-04-07

Unknown User (13:44:40): Unknown User (13:49:09): Unknown User (13:49:09): Unknown User (13:49:09): Unknown User (13:49:10): Unknown User (13:49:10): Unknown User (13:49:10): Unknown User (13:49:10): Unknown User (13:49:11): Unknown User (13:49:11): Unknown User (13:49:11): Unknown User (13:49:11): Unknown User (13:49:12): Unknown User (14:50:54): - Attachment: #342 ATACseqQC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jianhong/ATACseqQC > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:09:14): Unknown User (16:09:15): Unknown User (16:09:15): Unknown User (16:09:15): Unknown User (16:09:15): Unknown User (16:09:15): Unknown User (16:09:15): Unknown User (16:09:15): Unknown User (16:09:15): Unknown User (16:09:15): Unknown User (16:09:15): Unknown User (16:09:15): Unknown User (16:14:08): Unknown User (16:14:08): Unknown User (16:14:08): Unknown User (16:14:08): Unknown User (16:14:09): Unknown User (16:14:09): Unknown User (16:14:09): Unknown User (16:14:09): Unknown User (16:14:10): Unknown User (16:14:10): Unknown User (16:14:10): Unknown User (16:14:10): Unknown User (20:42:15): - Attachment: #343 CMEA: An R package for Systematic Exploration of Single-Cell Morphological Phenotypes from Transcriptomic Profile > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://bitbucket.org/isarnassiri/cmea > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (20:42:16): Unknown User (20:49:20): - Attachment: #344 CMEA: An R package for Systematic Exploration of Single-Cell Morphological Phenotypes from Transcriptomic Profile > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/isarnassiri/CMEA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-04-12

Unknown User (08:30:39): - Attachment: #345 CMEA: An R package for Systematic Exploration of Single-Cell Morphological Phenotypes from Transcriptomic Profile > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/isarnassiri/CMEA > Confirm the following by editing each check box to ‘[x]’ > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:30:40):

2017-04-14

Unknown User (15:18:12): - Attachment: #346 An R package and Shiny web application for longitudinal system suitability monitoring and quality control > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/eralpdogu/MSstatsQC > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:00:46): Unknown User (16:01:13):

2017-04-17

Unknown User (23:33:19): - Attachment: #347 StatePaintR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Simon-Coetzee/StatePaintr > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (23:33:20): Unknown User (23:37:11): - Attachment: #348 StatePaintR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Simon-Coetzee/StatePaintR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-04-18

Unknown User (05:51:10): Unknown User (05:51:10): Unknown User (05:55:08): Unknown User (11:41:29): - Attachment: #349 IsoformSwitchAnalyzeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/kvittingseerup/IsoformSwitchAnalyzeR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-04-21

Unknown User (06:09:55):

2017-04-23

Unknown User (17:10:05):

2017-04-24

Unknown User (14:31:41): Unknown User (14:31:41): Unknown User (14:31:41): Unknown User (14:31:41): Unknown User (14:31:42): Unknown User (15:57:28): - Attachment: #350 Combine: An ensemble method for RNA-Seq differential analysis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:57:28): Unknown User (16:04:31): - Attachment: #351 Combine: An ensemble method for RNA-Seq differential analysis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/DongmeiLi2017/Combine > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:04:31): Unknown User (16:09:56): - Attachment: #352 Combine: An ensemble method for RNA-Seq differential analysis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/DongmeiLi2017/Combine > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:09:57): Unknown User (16:35:57): - Attachment: #353 Combine: An ensemble method for RNA-Seq differential analysis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/DongmeiLi2017/Combine > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-04-27

Unknown User (16:39:57): - Attachment: #354 MIRA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:39:57): Unknown User (16:41:41): - Attachment: #355 MIRA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/databio/MIRA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-04-30

Unknown User (00:24:52): - Attachment: #356 w4mclassfilter > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/HegemanLab/w4m_ClassFilter > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (00:24:52): Unknown User (18:28:45): - Attachment: #357 w4mclassfilter > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/HegemanLab/w4mclassfilter > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-05-01

Aedin Culhane (12:09:18): > @Aedin Culhane has joined the channel

2017-05-02

Unknown User (08:06:22): Unknown User (14:54:52): - Attachment: #358 keggseq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/w-korani/keggseq > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:56:24): Unknown User (14:56:56):

2017-05-05

Unknown User (13:56:53): Unknown User (17:38:05): - Attachment: #359 multiMiR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/KechrisLab/multiMiR > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-05-06

Unknown User (19:25:34): Unknown User (19:25:34): Unknown User (19:25:34):

2017-05-07

Unknown User (07:24:51): - Attachment: #360 sgnesR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (07:24:52): Unknown User (07:34:20): - Attachment: #361 https://github.com/shaileshtripathi/sgnesR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:08:32): - Attachment: #362 sgnesR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/shaileshtripathi/sgnesR > Confirm the following by editing each check box to ‘[x]’ > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:16:48):

2017-05-08

Unknown User (06:47:21): Unknown User (14:35:21): Unknown User (14:45:08): - Attachment: #363 RTNsurvival: An R/Bioconductor package for survival analysis using transcriptional networks and regulons > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/csgroen/RTNsurvival/ > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-05-09

Unknown User (11:35:48): - Attachment: #364 zinbwave > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/drisso/zinbwave > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-05-10

Unknown User (12:17:13): - Attachment: #365 Onassis package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/eugeniaeueu/Onassis > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-05-12

Unknown User (07:20:30): Unknown User (10:12:26): - Attachment: #366 miRBaseConverter > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:12:27): Unknown User (10:20:03): - Attachment: #367 miRBaseConverter > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/xtsvm/miRBaseConverter > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-05-13

Unknown User (08:51:14): Unknown User (08:54:06): Unknown User (17:21:37): - Attachment: #368 sgnesR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/shaileshtripathi/sgnesR > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:21:38):

2017-05-14

Unknown User (13:19:54): - Attachment: #369 gene sim expression > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/shaileshtripathi/sgnesR > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:19:54):

2017-05-15

Unknown User (13:03:28): - Attachment: #370 microRNAome > • Repository: https://github.com/mccallm/microRNAome > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-05-17

Unknown User (06:36:32): - Attachment: #371 snpfier > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/isglobal-brge/snpfier/ > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:43:43):

2017-05-19

Unknown User (13:33:24): Unknown User (13:33:24):

2017-05-21

Unknown User (13:16:02): - Attachment: #372 gene sim > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/shaileshtripathi/sgnes > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:16:03): Unknown User (13:25:52): - Attachment: #373 gene simulation > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/shaileshtripathi/sgnesimR > Confirm the following by editing each check box to ‘[x]’ > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:44:52):

2017-05-22

Unknown User (09:11:45): - Attachment: #374 cytofWorkflow > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/gosianow/cytofWorkflow > • This package is a workflow. > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:56:26): - Attachment: #375 MetaCyto: an R package for the meta-analysis of cytometry data. > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • https://github.com/hzc363/MetaCyto > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-05-23

Unknown User (12:11:00): - Attachment: #376 retnfit > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hstern2/retnfit > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-05-24

Unknown User (15:45:06): - Attachment: #377 SCnorm > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/rhondabacher/SCnorm > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:39:58): Unknown User (17:56:23): - Attachment: #378 Rhdf5lib > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/grimbough/Rhdf5lib > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-05-26

Unknown User (10:30:29): - Attachment: #379 VULCAN: VirtUaL ChIP-Seq data Analysis using Networks > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/federicogiorgi/vulcan > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-05-29

Unknown User (23:20:03): - Attachment: #380 Trumpet > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/skyhorsetomoon/Trumpet > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (23:20:04): Unknown User (23:29:37): - Attachment: #381 Trumpet > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/skyhorsetomoon/Trumpet > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (23:29:37):

2017-05-30

Unknown User (06:45:06): - Attachment: #382 oneSENSE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yongkee/oneSENSE > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (07:03:02): Unknown User (09:33:34): - Attachment: #383 OnassisJavaLibs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository:https://github.com/eugeniaeueu/OnassisJavaLibs > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:39:12): Unknown User (13:18:27): - Attachment: #384 Scale4C > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/walter-ca/Scale4C > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-05-31

Unknown User (10:44:51): - Attachment: #385 zFPKM > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ronammar/zFPKM > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:56:08): - Attachment: #386 CEMiTool > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/csbl-usp/CEMiTool > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-06-01

Unknown User (16:33:38): Unknown User (16:34:34):

2017-06-02

Unknown User (19:10:59): - Attachment: #387 Submission of the “diffusion” R package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/b2slab/diffusion > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-06-03

Unknown User (05:31:15): Unknown User (05:31:23):

2017-06-04

Unknown User (11:18:46): - Attachment: #388 microbiome > GitHub repository of the package we wish to submit to Bioconductor > • Repository: https://github.com/microbiome/microbiome > > Note: this is a resubmission of the microbiome package in Bioconductor after the package has been completely rewritten following the feedback from H. Pages in 10/2014 (tracker.fhcrc.org/roundup/bioc_submit/issue1031). Therefore the verrsion number is 0.99.2 rather than 0.99.0 but the submission system has changed and as far as I can see, opening a new issue is the cleanest way to get forward. > > Confirm the following by editing each check box to ‘[x]’ > > • [X ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-06-05

Unknown User (10:35:18):

2017-06-06

Unknown User (10:07:54): - Attachment: #389 ClusterJudge > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/pasculescu/ClusterJudge.git > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:07:54): Unknown User (10:10:26): - Attachment: #390 ClusterJudge > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/pasculescu/ClusterJudge > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:17:04): Unknown User (11:29:45): Unknown User (11:29:45):

2017-06-07

Unknown User (19:42:59): - Attachment: #391 RProtoBufLib > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/RGLab/RProtoBufLib > Confirm the following by editing each check box to ‘[x]’ > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-06-08

Unknown User (04:36:38): Unknown User (05:32:03): - Attachment: #392 InterMineR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/intermine/intermineR/tree/master > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (05:32:03): Unknown User (05:49:57): - Attachment: #393 InterMineR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/intermine/InterMineR/tree/master > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:58:12): Unknown User (11:06:22): - Attachment: #394 HiCdiff > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/dozmorovlab/HiCdiff > > Confirm the following by editing each check box to ‘[x]’ > > • [X ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X ] The ‘devel’ branch for new packages and features. > • [X ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (23:42:00): - Attachment: #395 Optimal p-value weighting with independent information > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/mshasan/OPWeight > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-06-09

Unknown User (05:32:49): Unknown User (05:32:50): Unknown User (05:32:50): Unknown User (06:51:03): - Attachment: #396 Optimal p-value weighting with independent information (data and simulations) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/mshasan/OPWpaper > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (07:42:34):

2017-06-13

Unknown User (11:53:49): Unknown User (13:28:21):

2017-06-14

Unknown User (15:29:58): - Attachment: #397 consensusOV > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bhklab/consensusOV > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-06-18

Unknown User (15:03:09): - Attachment: #398 ComSeq: An ensemble method for RNA-Seq differential analysis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/DongmeiLi2017/ComSeq > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-06-20

Unknown User (20:52:54): - Attachment: #399 New package: survBootOutliers > • Repository: https://github.com/jonydog/survBootOutliers > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-06-22

Unknown User (11:08:35): - Attachment: #400 omicsPrint > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/molepi/omicsPrint > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:42:45): Unknown User (15:42:46): Unknown User (15:42:46): Unknown User (15:42:46):

2017-06-23

Unknown User (14:53:48):

2017-06-26

Unknown User (19:13:02): - Attachment: #401 EpiDISH > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/sjczheng/EpiDISH > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-06-27

Unknown User (06:46:16):

2017-06-28

Unknown User (14:08:34): - Attachment: #402 phenopath > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/kieranrcampbell/phenopath > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:42:01): - Attachment: #403 mfa > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/kieranrcampbell/mfa > Confirm the following by editing each check box to ‘[x]’ > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-06-29

Unknown User (05:36:04): - Attachment: #404 scmap > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hemberg-lab/scmap > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-06-30

Unknown User (03:17:17): - Attachment: #405 DEComplexDisease > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/menggf/DEComplexDisease.git > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (03:17:18): Unknown User (07:59:14): - Attachment: #406 Doscheda > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/brunocontrino/Doscheda > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:02:07): - Attachment: #407 TFARM > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/LiubaNM/TFARM > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > @mtmorgan

Unknown User (10:02:11): Unknown User (11:25:08): - Attachment: #408 DiffLogo > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/mgledi/DiffLogo > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-07-03

Unknown User (06:07:45): - Attachment: #409 TFARM(2) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/LiubaNM/TFARM > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > #184 > @mtmorgan

Unknown User (06:07:45): Unknown User (09:03:23): - Attachment: #410 seqcombo > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/GuangchuangYu/seqcombo > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-07-05

Unknown User (03:38:38): - Attachment: #411 M3C package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/crj32/M3C > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:48:02): Unknown User (21:55:24):

2017-07-07

Unknown User (05:22:16): Unknown User (05:22:16): Unknown User (05:22:16): Unknown User (05:22:16):

2017-07-08

Unknown User (23:28:22): - Attachment: #412 miRsponge > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/zhangjunpeng411/miRsponge > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-07-09

Unknown User (06:35:13): Unknown User (06:51:58): - Attachment: #413 beachmat > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/LTLA/beachmat > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-07-11

Unknown User (11:08:47): - Attachment: #414 SingleCellExperiment > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/drisso/SingleCellExperiment > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:43:07): - Attachment: #415 TMixClust > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/cbg-ethz/TMixClust > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (23:23:09): Unknown User (23:23:22):

2017-07-12

Unknown User (12:14:06): - Attachment: #416 RVS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/sherman5/RVS > > Confirm the following by editing each check box to ‘[x]’ > > • [X ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X ] The ‘devel’ branch for new packages and features. > • [ X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ X] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-07-13

Unknown User (00:34:33):

2017-07-14

Unknown User (07:16:51): - Attachment: #417 fix typo

Unknown User (12:32:25): Unknown User (12:32:25): Unknown User (12:32:26): Unknown User (12:32:26): Unknown User (16:05:09): Unknown User (16:05:09): Unknown User (19:06:27): - Attachment: #418 FSQN > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jenniferfranks/FSQN > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-07-17

Unknown User (06:36:10): - Attachment: #419 epivizrChart > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/epiviz/epivizrChart > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:04:05): Unknown User (11:04:14): Unknown User (11:10:09): Unknown User (19:25:59): - Attachment: #420 recountWorkflow > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/LieberInstitute/recountWorkflowBioc > > Note that this package is a workflow and not a software package. > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (19:26:00): Unknown User (19:28:54): - Attachment: #421 recountWorkflow > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/LieberInstitute/recountWorkflow > > Note that this package is a workflow and not a software package. > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-07-18

Unknown User (10:19:40): Unknown User (10:19:41): Unknown User (10:19:41):

2017-07-19

Unknown User (08:46:01):

2017-07-20

Unknown User (14:35:39): Unknown User (14:35:39):

2017-07-21

Unknown User (07:29:29): - Attachment: #422 AnimalGene2QTL > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (07:29:30): Unknown User (07:41:45): - Attachment: #423 https://github.com/liuyufong/AnimalGene2QTL > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (07:41:46): Unknown User (09:11:44): - Attachment: #424 AnimalGene2QTL > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:11:44): Unknown User (09:32:27): - Attachment: #425 AnimalGene2QTL > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:32:28): Unknown User (09:35:22): - Attachment: #426 AnimalGene2QTL > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:35:23): Unknown User (09:49:38): - Attachment: #427 AnimalGene2QTL:retrieve QTL,SNP and gene > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/liuyufong/AnimalGene2QTL > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-07-24

Unknown User (08:18:02): Unknown User (16:34:26): Unknown User (16:34:26): Unknown User (16:34:27):

2017-07-26

Ju Yeong Kim (14:37:12): > @Ju Yeong Kim has joined the channel

Unknown User (17:02:17): - Attachment: #428 TFHAZ > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/DEIB-GECO/TFHAZ > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:13:32): - Attachment: #429 DMCHMM > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:13:33): Unknown User (21:24:00): - Attachment: #430 DMCHMM > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/shokoohi/DMCHMM > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-07-28

Unknown User (04:48:46): - Attachment: #431 scPipe: a package for single cell RNA-seq data processing > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/LuyiTian/scPipe > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (06:21:39): - Attachment: #432 stageR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/statOmics/stageR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:25:48): Unknown User (13:25:49): Unknown User (13:25:50): Unknown User (15:59:33): - Attachment: #433 projectoR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/genesofeve/projectoR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-07-29

Unknown User (11:43:05): - Attachment: #434 GKnowMTest > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/sbstatgen/repo.gknowmtest.git > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:43:06): Unknown User (11:59:11): - Attachment: #435 GKnowMTest > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/sbstatgen/repo.gknowmtest > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:59:12): Unknown User (12:05:21): - Attachment: #436 GKnowMTest > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/sbstatgen/GKnowMTest > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-07-31

Unknown User (10:01:14): - Attachment: #437 IrisSpatialFeatures > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/gusef/Iris > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:01:14): Unknown User (10:09:10): - Attachment: #438 IrisSpatialFeatures > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/gusef/IrisSpatialFeatures > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-08-01

Unknown User (11:17:57): - Attachment: #439 DEP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/arnesmits/DEP > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-08-03

Unknown User (09:20:25): - Attachment: #440 EGSEA123 Workflow Package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/mritchie/EGSEA123 (note that this is a Workflow package, based on the afternoon workshop presented at BioC 2017 in Boston). > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-08-05

Unknown User (16:58:15): - Attachment: #441 DrugDiseaseNet > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:58:15): Unknown User (19:36:35): - Attachment: #442 DrugDiseaseNet > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/azampvd/DrugDiseaseNet > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using [Subversion][5] > (optionally [via GitHub][6]). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > DrugDiseaseNet_0.99.0.tar.gz

Unknown User (19:36:36): Unknown User (19:41:40): - Attachment: #443 DrugDiseaseNet > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/azampvd/DrugDiseaseNet > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-08-07

Unknown User (09:53:30): Unknown User (09:53:31): Unknown User (09:53:31): Unknown User (09:53:31): Unknown User (09:53:31): Unknown User (16:31:00): - Attachment: #444 SNPath > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/lschen-stat/SNPath > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:56:50): - Attachment: #445 cytolib > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/RGLab/cytolib > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:16:07): - Attachment: #446 apeglm > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/azhu513/apeglm > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-08-09

Unknown User (10:05:25):

2017-08-11

Unknown User (15:26:00): - Attachment: #447 SLICER > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jw156605/SLICER > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-08-12

Unknown User (20:27:19): - Attachment: #448 iterClust > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (20:27:20): Unknown User (20:55:44): - Attachment: #449 iterClust > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hd2326/iterClust > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-08-13

Unknown User (10:44:25): Unknown User (17:39:31): - Attachment: #450 ClonEvol > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hdng/clonevol > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-08-14

Unknown User (14:58:16): - Attachment: #451 iterClust > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hd2326/iterClust > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:58:17):

2017-08-15

Unknown User (07:15:33): - Attachment: #452 ChIPanalyser > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/patrickCNMartin/ChIPanalyser > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:40:47): Unknown User (22:06:54):

2017-08-16

Unknown User (04:46:27): Unknown User (04:46:31):

2017-08-18

Unknown User (18:17:31): - Attachment: #453 cbaf > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/armanshahrisa/cbaf > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-08-21

Unknown User (05:51:46): - Attachment: #454 amplican > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/valenlab/amplican > > Confirm the following by editing each check box to ‘[x]’ > > • [ x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x ] The ‘devel’ branch for new packages and features. > • [ x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (05:51:46): Unknown User (07:12:53): Unknown User (07:20:38): Unknown User (22:43:18): - Attachment: #455 DEComplexDisease > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/menggf/DEComplexDisease > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-08-22

Unknown User (12:12:25):

2017-08-23

Unknown User (04:38:39): - Attachment: #456 openPrimeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/matdoering/openPrimeR/ > > Confirm the following by editing each check box to ‘[x]’ > > • [ x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x ] The ‘devel’ branch for new packages and features. > • [ x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-08-24

Unknown User (09:39:09): Unknown User (09:39:38): - Attachment: #457 Rbowtie2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wzthu/Rbowtie2 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:07:24): Unknown User (15:38:31): - Attachment: #458 PROPS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/lhan22/PROPS > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-08-26

Unknown User (15:33:59):

2017-08-27

Unknown User (09:59:35): Unknown User (18:20:17): Unknown User (18:47:33): Unknown User (19:10:31): Unknown User (22:02:16):

2017-08-28

Unknown User (09:58:04): - Attachment: #459 phantasus > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ctlab/phantasus > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:10:09): - Attachment: #460 SeqSQC formal review > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Liubuntu/SeqSQC > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > SeqSQC is an Experiment Data package.

2017-08-29

Unknown User (02:38:55): - Attachment: #461 SPONGE package for inferring genome-wide competing endogenous RNA networks > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/mlist/SPONGE > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (03:47:55): - Attachment: #462 miRmine > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/duxan/miRmine > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (05:00:08): Unknown User (15:26:38): - Attachment: #463 methyvim > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/nhejazi/methyvim > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:32:19): Unknown User (16:33:01): - Attachment: #464 methyvim > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/nhejazi/methyvimData > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:39:13): - Attachment: #465 MetaCyto > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:39:14): Unknown User (18:42:44): - Attachment: #466 MetaCyto > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hzc363/MetaCyto > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:42:45): Unknown User (21:27:30): - Attachment: #467 loci2path > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/StanleyXu/loci2path > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-08-31

Unknown User (19:30:48): - Attachment: #468 Affinity Network Fusion (ANF) > • Repository: https://github.com/BeautyOfWeb/ANF > • AdditionalPackage: https://github.com/BeautyOfWeb/HarmonizedTCGAData > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (19:30:49): Unknown User (20:00:27): - Attachment: #469 Affinity Network Fusion (ANF) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/BeautyOfWeb/ANF > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-09-01

Unknown User (05:35:26): - Attachment: #470 EpiCluster > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/JoshuaTian/EpiCluster > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-09-04

Unknown User (13:15:51): - Attachment: #471 anota2seq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:15:51): Unknown User (13:29:25): - Attachment: #472 anota2seq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ChrOertlin/anota2seq/ > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-09-05

Unknown User (12:22:01): Unknown User (12:22:20): Unknown User (13:50:38): Unknown User (21:21:03): - Attachment: #473 new submission of experiment data package, MSstatsBioData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/MeenaChoi/MSstatsBioData > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-09-06

Unknown User (16:12:59): - Attachment: #474 package rhdf5client submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/sampoll/rhdf5client > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-09-07

Unknown User (13:09:13): - Attachment: #475 BASiCS (Bayesian Analysis of Single Cell Sequencing data) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/catavallejos/BASiCS > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-09-08

Unknown User (13:23:42): - Attachment: #476 package restfulSE submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/shwetagopaul92/restfulSE > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:25:44):

2017-09-09

Unknown User (06:55:27): - Attachment: #477 progeny: pathway activity inference from gene expression data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/saezlab/progeny > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:05:58): Unknown User (15:44:00): Unknown User (15:46:02): Unknown User (15:46:33):

2017-09-10

Unknown User (22:52:54): - Attachment: #478 submitting ontoProc package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/vjcitn/ontoProc > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-09-11

Unknown User (21:17:15): - Attachment: #479 submitting tenXplore package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/vjcitn/tenXplore > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-09-12

Unknown User (06:39:29): - Attachment: #480 Update the template to new source control material

2017-09-14

Unknown User (06:42:48): - Attachment: #481 panelcn.mops > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bioinf-jku/panelcn.mops > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:56:59): - Attachment: #482 seqCAT > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/fasterius/seqCAT > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Subversion > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-09-15

Unknown User (15:10:14): Unknown User (15:10:14):

2017-09-18

Unknown User (12:34:16): - Attachment: #483 multiMiR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/KechrisLab/multiMiR > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:34:17): Unknown User (17:23:48): - Attachment: #484 oncomix > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/dpique/oncomix > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-09-19

Unknown User (07:48:17): - Attachment: #485 methimpute > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ataudt/methimpute > > Confirm the following by editing each check box to ‘[x]’ > > • [ x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x ] The ‘devel’ branch for new packages and features. > • [ x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-09-20

Unknown User (16:33:31): - Attachment: #486 survBootOutliers > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jonydog/survBootOutliers > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:33:32): Unknown User (20:12:08):

2017-09-21

Unknown User (02:41:15): - Attachment: #487 TnT: interactive visualization for track-based genomic data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Marlin-Na/TnT > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:13:51): - Attachment: #488 JASPAR2018 data package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ge11232002/JASPAR2018 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-09-22

Unknown User (03:49:19): - Attachment: #489 scPipe: a package for single cell RNA-seq data processing and quality control > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/LuyiTian/scPipe > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:40:06): - Attachment: #490 chromswitch > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/sjessa/chromswitch > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:59:31): - Attachment: #491 Roma > • Repository: https://github.com/klarakaleb/roma > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor [Package Submission][2] > instructions. My package is consistent with the Bioconductor > [Package Guidelines][1]. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the [support site][3] for issues that users may > have, subscribing to the [bioc-devel][4] mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using [Git][5] > (optionally [via GitHub][6]).

Unknown User (16:26:41): - Attachment: #492 ivygapSE package submitted > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/vjcitn/ivygapSE > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-09-23

Unknown User (12:11:20): - Attachment: #493 hmdbQuery package submitted > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/vjcitn/hmdbQuery > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-09-24

Unknown User (09:57:59): Unknown User (09:59:31): Unknown User (22:52:07): - Attachment: #494 BiodivoTools package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/MPiet11/BiodivoTools > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-09-25

Unknown User (10:56:31): Unknown User (10:56:34): Unknown User (14:32:02): - Attachment: #495 bcSeq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jl354/bcSeq > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:46:12): - Attachment: #496 neoantigenR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/tangshao2016/neoantigenR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-09-26

Unknown User (09:05:56): - Attachment: #497 MulEA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/koralgooll/MulEA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-09-27

Unknown User (16:23:35): Unknown User (16:30:48): Unknown User (16:46:00): Unknown User (16:53:07): Unknown User (16:53:38): Unknown User (16:54:32): Unknown User (16:54:39): Unknown User (17:21:56): Unknown User (17:22:52): Unknown User (17:22:56):

2017-09-28

Unknown User (14:04:54): - Attachment: #498 package restfulSEData submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/shwetagopaul92/restfulSEData > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:28:14): - Attachment: #499 chromVAR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/GreenleafLab/chromVAR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-09-29

Unknown User (22:04:11): - Attachment: #500 Guitar2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/laureniezhang/Guitar2 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-10-02

Unknown User (06:41:38): - Attachment: #501 pcxn > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hidelab/pcxn > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:48:04): Unknown User (11:11:38): - Attachment: #502 RcisTarget > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/aertslab/RcisTarget.hg19.motifDatabases.cisbpOnly.500bp > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:59:25): - Attachment: #503 https://github.com/arthurvinx/transcriptogramer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:59:26): Unknown User (19:03:32): - Attachment: #504 https://github.com/arthurvinx/transcriptogramer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/arthurvinx/transcriptogramer > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-10-03

Unknown User (13:45:35): - Attachment: #505 ATACFlow > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wzthu/ATACFlow > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-10-04

Unknown User (03:51:42): - Attachment: #506 New package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/LauraPS1/TFEA.ChIP > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (04:00:22): Unknown User (06:57:21): - Attachment: #507 scfind > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hemberg-lab/scfind > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (07:42:47): - Attachment: #508 geno2proteo > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yaoyong02/geno2proteo > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:58:24): - Attachment: #509 MAGeCKFlute > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/WubingZhang/MAGeCKFlute > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:59:53): - Attachment: #510 mpra > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hansenlab/mpra > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:41:32): - Attachment: #511 chromloop > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ibn-salem/chromloop > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:53:29): Unknown User (11:53:30): Unknown User (11:53:31): Unknown User (11:53:31): Unknown User (12:02:38): Unknown User (12:11:25): Unknown User (17:25:45): - Attachment: #512 topdownr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/sgibb/topdownrdata > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic proteomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-10-05

Unknown User (14:36:04): - Attachment: #513 dmrseq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/kdkorthauer/dmrseq > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:00:33): - Attachment: #514 DelayedMatrixStats > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/PeteHaitch/DelayedMatrixStats > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (20:13:32): - Attachment: #515 runibic: UniBic biclustering algorithm for R > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/athril/runibic > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (20:44:31): - Attachment: #516 FastProjectR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/YosefLab/FastProjectR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-10-06

Unknown User (12:44:44): - Attachment: #517 GOfuncR package submission > • Repository: https://github.com/sgrote/GOfuncR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:44:45): Unknown User (12:59:14): - Attachment: #518 Submission of package GOfuncR > • Repository: https://github.com/sgrote/GOfuncR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:42:35): - Attachment: #519 bnbc > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hansenlab/bnbc > > Confirm the following by editing each check box to ‘[x]’ > > • [X ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X ] The ‘devel’ branch for new packages and features. > • [X ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:13:25): - Attachment: #520 slalom > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/PMBio/slalom > > [NB: I am submitting this package under my account, though it is currently hosted through a GitHub account belonging to the Stegle Group and EMBL-EBI] > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > [NB: there is currently one warning, which we believe to be an issue with GSEABase as reported on Bioc-devel mailing list in the last 24 hours or so] > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (19:30:31): - Attachment: #521 LineagePulse > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/YosefLab/LineagePulse > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (22:45:11): - Attachment: #522 curatedTCGAData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/waldronlab/curatedTCGAData > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-10-10

Unknown User (07:39:53): - Attachment: #523 GMQL > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/DEIB-GECO/RGMQL > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (07:39:54): Unknown User (07:57:52): - Attachment: #524 RGMQL > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/DEIB-GECO/RGMQL > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:42:13): Unknown User (11:12:38): Unknown User (11:17:58): - Attachment: #525 pcxnData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:17:58): Unknown User (11:22:41): - Attachment: #526 pcxnData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hidelab/pcxnData > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:57:15): Unknown User (12:27:53): - Attachment: #527 scFeatureFilter > Hi, > I wish to submit the following package to Bioconductor: > > • Repository: https://github.com/gdevailly/scFeatureFilter > > It is my first R package, I apologize for all the silly mistake I may have left uncorrected. > Many thanks for your time, > > Guillaume > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:06:01): Unknown User (18:06:02): Unknown User (18:06:03): Unknown User (18:06:03): Unknown User (18:06:04): Unknown User (18:06:05): Unknown User (18:06:06): Unknown User (18:06:07): Unknown User (18:06:08):

2017-10-11

Unknown User (06:33:16): - Attachment: #528 gep2pep > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/franapoli/gep2pep > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:14:02): - Attachment: #529 ATACpipe > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wzthu/ATACpipe > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-10-12

Unknown User (08:49:49): - Attachment: #530 spbtest3 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor/spbtest3 > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:49:52): Unknown User (08:54:10): - Attachment: #531 Test > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor/spbtest3 > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:54:12):

2017-10-13

Unknown User (13:31:11): Unknown User (13:32:14): Unknown User (13:58:39):

2017-10-16

Unknown User (11:08:21): - Attachment: #532 HMP16SData > Hi guys, this is an ExperimentHub package so maybe review should be done by @lshep or @vobencha. Data are there on S3 already and the metadata.csv file has been prepared as well. Will just need to add the resources to production to evaluate the vignette. Both Build and Check pass for me : ) It is a tiny package, can go into release or devel – either is fine. Thanks x 10^6 > > These commands, to look at the objects quickly without ExperimentHub: > > BiocInstaller::biocLite("waldronlab/HMP16SData") > library(HMP16SData) > data("20171011.V13") > data("20171011.V35") > V13 > V35 > > > • Repository: https://github.com/waldronlab/HMP16SData > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-10-20

Unknown User (11:03:29): - Attachment: #533 signet R package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/CMPG/signet > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:06:27): - Attachment: #534 Key2Enrich > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:06:28): Unknown User (18:07:19): - Attachment: #535 Key2Enrich > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:07:20): Unknown User (18:09:01): - Attachment: #536 Key2Enrich > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:09:58): - Attachment: #537 Key2Enrich > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:09:59):

2017-10-21

Unknown User (19:27:06):

2017-10-22

Unknown User (13:09:44): Unknown User (13:09:45): Unknown User (13:09:46): Unknown User (13:09:46): Unknown User (13:09:47): Unknown User (13:09:48): Unknown User (13:09:49): Unknown User (13:09:50): Unknown User (13:09:50): Unknown User (13:09:51): Unknown User (13:09:52): Unknown User (13:09:52): Unknown User (13:09:53): Unknown User (13:09:54): Unknown User (13:09:54): Unknown User (13:09:55): Unknown User (13:09:55): Unknown User (13:09:56): Unknown User (13:09:57): Unknown User (13:09:58): Unknown User (13:09:58):

2017-10-25

Unknown User (16:46:32): Unknown User (16:50:33): Unknown User (16:52:10): Unknown User (17:42:06): Unknown User (17:50:31): Unknown User (17:50:31): Unknown User (17:50:32): Unknown User (18:06:37): Unknown User (18:28:25): Unknown User (22:50:51): - Attachment: #538 MACPET > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/IoannisVardaxis/MACPET > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-10-26

Unknown User (13:41:59): Unknown User (17:43:08):

2017-10-27

Unknown User (13:50:20): Stian Lågstad (15:51:03): > @Stian Lågstad has joined the channel

2017-10-29

Unknown User (09:57:39): Unknown User (09:57:40): Unknown User (14:49:59):

2017-10-30

Unknown User (00:15:31): - Attachment: #539 affyCustomCDF > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/UofLBioinformatics/affyCustomCDF > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (00:15:32):

2017-11-01

Unknown User (17:13:46): - Attachment: #540 biothings > @newgene :) > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/biothings/biothings_client.R > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:13:46):

2017-11-03

Unknown User (11:30:14): - Attachment: #541 drawProteins > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/brennanpincardiff/drawProteins > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:10:10): - Attachment: #542 MetaNeighbor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/mm-shah/MetaNeighbor > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-11-04

Unknown User (22:08:28): - Attachment: #543 Key2Enrich R package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (22:08:29): Unknown User (22:46:25): - Attachment: #544 Key2Enrich: An all-in-one R/Bioconductor package for gene list enrichment analysis and pathway visualization > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ppdragondw/Key2Enrich > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-11-05

Unknown User (20:23:39): - Attachment: #545 Numero > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/sahmri-molar/numero > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (20:23:40): Unknown User (20:30:36): - Attachment: #546 Numero > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/sahmri-molar/Numero > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-11-06

Unknown User (15:11:38): - Attachment: #547 BASiNET > • Repository: https://github.com/EricIto/BASiNET > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:12:21): Unknown User (15:12:33):

2017-11-08

Unknown User (09:37:51): Unknown User (15:23:54): - Attachment: #548 BioThingsClient > @newgene > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/biothings/BioThingsClient.R > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:23:55): Unknown User (16:25:19): - Attachment: #549 survcomp > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bhklab/survcomp > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:02:11): Unknown User (23:26:41): - Attachment: #550 CHARGE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/BenjaminAdelaide/CHARGE > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-11-13

Unknown User (04:32:32): - Attachment: #551 pace > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/MalgorzataOles/pace > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor [Package Submission][2] > instructions. My package is consistent with the Bioconductor > [Package Guidelines][1]. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the [support site][3] for issues that users may > have, subscribing to the [bioc-devel][4] mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using [Git][5] > (optionally [via GitHub][6]). > > For help with submitting your package, please subscribe and post questions > to the [bioc-devel][4] mailing list.

Unknown User (06:10:33): - Attachment: #552 mCSEAdata > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jordimartorell/mCSEAdata > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-11-14

Unknown User (08:52:03):

2017-11-15

Unknown User (04:46:48): - Attachment: #553 New package: flowLearn > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/mlux86/flowLearn > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:08:28): - Attachment: #554 IMMAN > https://github.com/jafarilab/IMMAN

Unknown User (10:08:28): Unknown User (18:25:26): - Attachment: #555 ChIPSeqSpike: ChIP-Seq data scaling according to spike-in control > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/descostesn/ChIPSeqSpike > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-11-17

Unknown User (02:48:18):

2017-11-21

Unknown User (05:18:05): - Attachment: #556 IMMAN > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by > IMMAN_1.0.0.tar.gz > editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (05:18:06): Unknown User (13:14:34): - Attachment: #557 SelexGLM > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/BussemakerLab/SelexGLM > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Marcel Ramos Pérez (20:13:29): > removed an integration from this channel: github

2017-11-22

Unknown User (08:18:21): - Attachment: #558 TTMap > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:20:32): Unknown User (08:35:22): - Attachment: #559 TTMap > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jeitziner/TTMap > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:23:10): - Attachment: #560 IMMAN > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:12:01): Unknown User (10:21:30): - Attachment: #561 HTSanalyzeR2: A R/Bioconductor package for gene set enrichment and network analysis of various high-throughput data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/CityUHK-CompBio/HTSanalyzeR2 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:34:06): Unknown User (16:34:06): Unknown User (16:34:07): Unknown User (16:34:08): Unknown User (16:34:08): Unknown User (18:42:31): - Attachment: #562 flowCut > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jmeskas/flowCut > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-11-26

Unknown User (02:44:36): - Attachment: #563 IMMAN > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jafarilab/IMMAN > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (02:44:39): Unknown User (03:40:16): - Attachment: #564 IMMAN > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jafarilab/IMMAN > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (07:54:48): - Attachment: #565 IMMAN > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jafarilab/IMMAN > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (07:54:50):

2017-11-28

Unknown User (05:06:46): - Attachment: #566 IMMAN > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jafarilab/IMMAN > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (05:06:47): Unknown User (09:55:39): - Attachment: #567 enrichplot > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/GuangchuangYu/enrichplot > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Simina Boca (14:27:52): > @Simina Boca has joined the channel

Unknown User (18:43:33): - Attachment: #568 BloodCancerMultiOmics2017 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/MalgorzataOles/BloodCancerMultiOmics2017 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor [Package Submission][2] > instructions. My package is consistent with the Bioconductor > [Package Guidelines][1]. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the [support site][3] for issues that users may > have, subscribing to the [bioc-devel][4] mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using [Git][5] > (optionally [via GitHub][6]). > > For help with submitting your package, please subscribe and post questions > to the [bioc-devel][4] mailing list.

Unknown User (18:51:39):

2017-11-29

Matthew McCall (09:42:22): > @Matthew McCall has joined the channel

Unknown User (15:47:22):

2017-12-01

Unknown User (18:44:38): - Attachment: #569 GDCRNATools > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Jialab-UCR/GDCRNATools > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-12-02

Unknown User (23:22:47): - Attachment: #570 r2cytoscape > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/cytoscape/r2cytoscape > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-12-04

Unknown User (15:04:38): - Attachment: #571 omicplotR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/dgiguer/omicplotR > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-12-07

Unknown User (11:23:47):

2017-12-08

Charlotte Soneson (04:20:56): > @Charlotte Soneson has joined the channel

2017-12-10

Unknown User (18:52:25): - Attachment: #572 BEARscc > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/seversond12/BEARscc.git > > Confirm the following by editing each check box to ‘[x]’ > > • [X ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X ] The ‘devel’ branch for new packages and features. > • [ X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:52:26): Unknown User (18:58:23): - Attachment: #573 BEARscc > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > Repository: https://github.com/seversond12/BEARscc > > Confirm the following by editing each check box to ‘[x]’ > > [X ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > [ X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > [X ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > [X ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > [X ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > [X ] The ‘devel’ branch for new packages and features. > [ X] The stable ‘release’ branch, made available every six > months, for bug fixes. > [X ] Bioconductor version control using Git > (optionally via GitHub). > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:58:24): Unknown User (19:05:28): - Attachment: #574 BEARscc > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > Repository: https://github.com/seversond12/BEARscc > > Confirm the following by editing each check box to ‘[x]’ > > [X ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > [ X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > [X ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > [X ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > [X ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > [X ] The ‘devel’ branch for new packages and features. > [ X] The stable ‘release’ branch, made available every six > months, for bug fixes. > [X ] Bioconductor version control using Git > (optionally via GitHub). > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-12-11

Unknown User (06:41:02): - Attachment: #575 ddPCRclust > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bgbrink/ddPCRclust > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:00:12): - Attachment: #576 martini > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hclimente/martini/ > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:33:48): Unknown User (20:39:43): - Attachment: #577 TCGAbiolinksGUI.data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/BioinformaticsFMRP/TCGAbiolinksGUI.data > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-12-12

Unknown User (00:27:25): - Attachment: #578 tidytree: A Tidy Tool for Phylogenetic Tree Data Manipulation > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/GuangchuangYu/tidytree > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-12-13

Unknown User (16:44:08): Unknown User (16:44:09): Unknown User (16:44:10): Unknown User (16:44:11):

2017-12-14

Unknown User (06:10:48): Unknown User (17:37:52): - Attachment: #579 iCNV > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/zhouzilu/iCNV > Package is in the package folder. > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:37:53): Unknown User (17:40:44): - Attachment: #580 iCNV > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/zhouzilu/iCNV/tree/master/package > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:40:44): Unknown User (17:45:49): - Attachment: #581 iCNV > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/zhouzilu/iCNV_bioconductor > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:45:50): Unknown User (17:52:11): - Attachment: #582 iCNV > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/zz327/iCNV > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-12-15

Unknown User (16:32:52): - Attachment: #583 StatePaintR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Simon-Coetzee/StatePaintR > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:32:53): Unknown User (16:37:50): Unknown User (18:24:44):

2017-12-18

Unknown User (19:09:46): - Attachment: #584 MLML2R > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/samarafk/MLML2R > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-12-19

Unknown User (15:14:19): Unknown User (15:47:09):

2017-12-20

Unknown User (12:03:03): - Attachment: #585 Bias-free Footprint Enrichment Test (BiFET): A robust statistical test for transcription factor footprint data analyses > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/UcarLab/BiFET > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-12-21

Unknown User (08:22:33): - Attachment: #586 DropletUtils > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/MarioniLab/DropletUtils > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:05:43): - Attachment: #587 spbtest4 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor/spbtest4 > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:25:11): Unknown User (13:18:18): - Attachment: #588 CTDquerier > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/isglobal-brge/CTDquerier > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-12-22

Unknown User (08:28:02): - Attachment: #589 New package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/JMF47/recountNNLSdata > Confirm the following by editing each check box to ‘[x]’ > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:32:10): - Attachment: #590 DEScan2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/drighelli/DEScan2 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-12-25

Unknown User (20:07:21): - Attachment: #591 TarMet > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hcji/TarMet > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2017-12-30

Unknown User (23:39:09): - Attachment: #592 scmeth > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/aryeelab/scmeth > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-01-02

Unknown User (13:03:14): Unknown User (13:03:15):

2018-01-03

Unknown User (06:37:26): - Attachment: #593 RGMQLlib > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/DEIB-GECO/RGMQLlib > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-01-04

Unknown User (10:31:24): - Attachment: #594 kissDE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://umr5558-gitlab.univ-lyon1.fr:10443/aursiber/kissDE.git > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:31:26): Unknown User (10:36:08): - Attachment: #595 kissDE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://umr5558-gitlab.univ-lyon1.fr:10443/aursiber/kissDE > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:36:09): Unknown User (11:01:39): - Attachment: #596 kissDE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/aursiber/kissDE > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:03:13):

2018-01-05

Unknown User (19:31:11): - Attachment: #597 TCGAutils > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/waldronlab/TCGAutils > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-01-06

Unknown User (10:28:39): - Attachment: #598 submitting pogos package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/vjcitn/pogos > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-01-07

Unknown User (07:04:49): - Attachment: #599 gsean > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/dongminjung/gsean > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-01-08

Unknown User (08:29:31): - Attachment: #600 MDTS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/JMF47/MDTS > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:42:29): - Attachment: #601 Submission of “srnadiff” to BioConductor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/mzytnicki/srnadiff > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:54:54): - Attachment: #602 netSmooth: A Network smoothing based method for Single Cell RNA-seq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/BIMSBbioinfo/netsmooth > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:54:56): Unknown User (09:56:31): - Attachment: #603 netSmooth: A Network smoothing based method for Single Cell RNA-seq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/BIMSBbioinfo/netSmooth > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:28:56): - Attachment: #604 retrofit > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hstern2/retnfit > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:28:57): Unknown User (10:46:12): Unknown User (12:41:01): - Attachment: #605 Trendy > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/rhondabacher/Trendy > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (19:18:13):

2018-01-09

Unknown User (17:14:09):

2018-01-10

Unknown User (04:49:20): - Attachment: #606 BioDataome > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/mensxmachina/BioDataome > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-01-11

Unknown User (13:12:39): Unknown User (13:12:39): Unknown User (16:03:00): Unknown User (16:54:35): - Attachment: #607 tRNAscan2GRanges > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/FelixErnst/tRNAscan2GRanges > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-01-13

Unknown User (07:12:25): - Attachment: #608 Sconify > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (07:12:26): Unknown User (07:21:38): - Attachment: #609 Sconify > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (07:21:39): Unknown User (07:24:57): - Attachment: #610 Sconify > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/tjburns08/Sconify > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-01-14

Unknown User (11:28:32): - Attachment: #611 TENxBrainData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor/TENxBrainData > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:03:28): Unknown User (14:15:12):

2018-01-15

Unknown User (08:20:03): - Attachment: #612 FELLA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/b2slab/FELLA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-01-16

Unknown User (07:02:50): - Attachment: #613 HiPathia > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/babelomics/hipathia > > Confirm the following by editing each check box to ‘[x]’ > > • [ x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x ] The ‘devel’ branch for new packages and features. > • [ x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:17:47): - Attachment: #614 hpAnnot > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/babelomics/hpAnnot > > Confirm the following by editing each check box to ‘[x]’ > > • [ x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x ] The ‘devel’ branch for new packages and features. > • [ x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-01-17

Unknown User (17:47:56): Unknown User (17:47:57): Unknown User (17:47:57): Unknown User (17:47:58):

2018-01-18

Unknown User (06:19:28): Unknown User (07:40:37): - Attachment: #615 PowerExplorer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/xuqiao93/PowerExplorer > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:17:46): - Attachment: #616 hgu133plus2CellScore > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/nmah/hgu133plus2CellScore > > Confirm the following by editing each check box to ‘[x]’ > > • [X ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X ] The ‘devel’ branch for new packages and features. > • [ X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-01-19

Unknown User (00:35:59): - Attachment: #617 SEPIRA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/YC3/SEPIRA-package > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (00:36:00): Unknown User (00:39:43): - Attachment: #618 SEPIRA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/YC3/SEPIRA-package > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (00:39:44): Unknown User (00:43:37): - Attachment: #619 SEPIRA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/YC3/SEPIRA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:46:46): Unknown User (16:14:26): Unknown User (17:54:03):

2018-01-22

Unknown User (17:20:37): - Attachment: #620 RNAdecay > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/reedssorenson/RNAdecay > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-01-23

Unknown User (03:55:52): - Attachment: #621 iteremoval > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/cihga39871/iteremoal.R > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (03:55:52): Unknown User (05:22:26): - Attachment: #622 iteremoval > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/cihga39871/iteremoval > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:33:47): - Attachment: #623 fsgor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/DanWiebe/fsgor > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-01-24

Unknown User (00:38:39): Unknown User (06:53:08): Unknown User (06:53:08): Unknown User (06:53:09): Unknown User (19:21:10): - Attachment: #624 NADDA (non-alignment domain detection algorithm) for R > https://github.com/armenabnousi/naddaR

Unknown User (19:21:12):

2018-01-25

Unknown User (09:25:46): - Attachment: #625 kBET > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/theislab/kBET > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:50:41): - Attachment: #626 NADDA (non-alignment domain detection algorithm for protein sequences) > https://github.com/armenabnousi/naddaR

Unknown User (16:46:09): - Attachment: #627 GeneStructureTools Submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/betsig/GeneStructureTools > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (20:57:30):

2018-01-28

Unknown User (19:22:58): - Attachment: #628 adaptest > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wilsoncai1992/adaptest > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-01-29

Unknown User (10:42:53): - Attachment: #629 bdChemo > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/YiyiLiu1/bdChemo > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-01-30

Unknown User (11:28:14): Unknown User (19:00:55): - Attachment: #630 Reproducible GSEA Benchmarking > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/waldronlab/GSEABenchmarkeR > > Confirm the following by editing each check box to ‘[x]’ > > • [ x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x ] The ‘devel’ branch for new packages and features. > • [ x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-01-31

Unknown User (17:58:29): - Attachment: #631 SDAMS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:58:29): Unknown User (20:44:50): - Attachment: #632 SDAMS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Stat-Li/SDAMS > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (20:44:51): Unknown User (20:58:48): - Attachment: #633 SDAMS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Stat-Li/SDAMS > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-02-01

Unknown User (05:51:54): - Attachment: #634 SEQprocess > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/SYSMED/SEQprocess > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (06:00:58):

2018-02-02

Unknown User (15:25:55): - Attachment: #635 powerTCR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hillarykoch/powerTCR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:09:39): - Attachment: #636 MetaGxOvarian > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bhklab/MetaGxOvarian > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-02-03

Unknown User (12:24:11): Unknown User (12:24:11): Unknown User (12:24:12): Unknown User (12:24:13): Unknown User (12:24:14): Unknown User (12:24:15): Unknown User (12:24:15): Unknown User (12:24:17):

2018-02-04

Unknown User (19:16:27): - Attachment: #637 AIRs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bioinfo16/AIRs > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (19:26:15):

2018-02-05

Unknown User (05:33:42): - Attachment: #638 diffcoexp > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hidelab/diffcoexp > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:32:22): - Attachment: #639 Geneplastdata submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/sheylatrefflich/Geneplastdata > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:32:23): Unknown User (12:48:29): - Attachment: #640 Geneplastdata submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/sheylatrefflich/geneplast.data.string.v91 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-02-06

Unknown User (13:19:03):

2018-02-07

Unknown User (05:51:13): - Attachment: #641 perturbatr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/cbg-ethz/perturbatr > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-02-08

Unknown User (06:17:02): - Attachment: #642 DominoEffect > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/peterblattmann/DominoEffect > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:06:30): Unknown User (14:38:56): - Attachment: #643 phenopredict > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/leekgroup/phenopredict > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:34:23):

2018-02-09

Unknown User (15:44:41): - Attachment: #644 Rgin > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hclimente/Rgin > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-02-10

Unknown User (12:55:28): - Attachment: #645 tRNAscanImport > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/FelixErnst/tRNAscanImport > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:44:16):

2018-02-11

Unknown User (14:39:23): - Attachment: #646 MBttest > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > https://github.com/Yuande/MBttest/tree/master/.ssh/MBttest_1.7.1.tar.gz > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor [Package Submission][2] > instructions. My package is consistent with the Bioconductor > [Package Guidelines][1]. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the [support site][3] for issues that users may > have, subscribing to the [bioc-devel][4] mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using [Git][5] > (optionally [via GitHub][6]).

Unknown User (14:39:24): Unknown User (15:00:50): - Attachment: #647 MBttest > /Users/yuandet/Documents/MBttest_1.7.1.tar.gz > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor [Package Submission][2] > instructions. My package is consistent with the Bioconductor > [Package Guidelines][1]. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the [support site][3] for issues that users may > have, subscribing to the [bioc-devel][4] mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using [Git][5] > (optionally [via GitHub][6]).

Unknown User (15:00:51):

2018-02-12

Unknown User (08:29:10): - Attachment: #648 GARS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/BioinfoMonzino/GARS > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:57:48): Unknown User (09:57:49): Unknown User (09:57:50): Unknown User (09:57:51): Unknown User (09:57:52): Unknown User (09:57:53): Unknown User (12:39:01): - Attachment: #649 mvGST 1.14.0 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/johnrstevens/mvGST > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:50:44): Unknown User (15:50:55):

2018-02-13

Unknown User (02:25:03): - Attachment: #650 FastqCleaner > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/leandroroser/FastqCleaner > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (06:36:25): Unknown User (20:33:43):

2018-02-14

Unknown User (10:46:58): - Attachment: #651 SummarizedBenchmark > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/areyesq89/SummarizedBenchmark > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Stian Lågstad (10:49:21): > @Stian Lågstad has left the channel

2018-02-16

Laurent Gatto (14:56:28): > @Laurent Gatto has joined the channel

Unknown User (16:31:16): Unknown User (16:31:17): Unknown User (16:31:19):

2018-02-19

Unknown User (13:33:04): - Attachment: #652 RSeqAn > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/compbiocore/RSeqAn > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-02-22

Unknown User (02:34:18): - Attachment: #653 DEsingle > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/miaozhun/DEsingle > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:34:52): - Attachment: #654 iCNV > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/zhouzilu/iCNV > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:31:48): - Attachment: #655 ViDGER > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/btmonier/vidger > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (21:42:09): - Attachment: #656 MetaGxbreast > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > https://github.com/bhklab/MetaGxBreast > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [ x The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-02-23

Unknown User (11:56:37): - Attachment: #657 CHIC: CHIp-seq quality Control package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/carmencita/CHIC > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:27:03): Unknown User (18:29:19): - Attachment: #658 ViDGER > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (22:50:12): Unknown User (22:50:39):

2018-02-26

Unknown User (11:57:35):

2018-02-27

Unknown User (12:42:11): - Attachment: #659 CAGEfightR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/MalteThodberg/CAGEfightR > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-02-28

Unknown User (11:21:01): Unknown User (14:39:42): Unknown User (17:27:08): Unknown User (17:27:10): Unknown User (17:27:10): Unknown User (17:27:11): Unknown User (17:27:13): Unknown User (17:27:14):

2018-03-01

Unknown User (13:33:18): - Attachment: #660 slinky > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/VanAndelInstitute/slinky > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-03-02

Unknown User (07:35:51): Unknown User (15:52:45): - Attachment: #661 GDSArray > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:52:46): Unknown User (15:54:41): - Attachment: #662 GDSArray > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor/GDSArray > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:54:42): Unknown User (16:03:02): - Attachment: #663 GDSArray > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor/GDSArray > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:03:03): Unknown User (16:08:44): - Attachment: #664 GDSArray > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor/GDSArray > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:13:55): Unknown User (16:14:31): Unknown User (16:21:36):

2018-03-05

Unknown User (01:48:27): - Attachment: #665 Multi-dataset model-based differential expression proteomics analysis pipeline > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yuliya8k/MultiMat/e > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:48:26): - Attachment: #666 decontam > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/benjjneb/decontam > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-03-06

Unknown User (09:43:14): - Attachment: #667 ASICSdata > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/GaelleLefort/ASICSdata > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:20:45): - Attachment: #668 singscore > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/DavisLaboratory/singscore > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-03-07

Unknown User (00:26:25): Unknown User (00:46:20): Unknown User (00:51:14): - Attachment: #669 SEQprocess > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/SYSMED/SEQprocess > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (00:51:15): Unknown User (00:54:55): Unknown User (02:16:37): - Attachment: #670 plyranges > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/sa-lee/plyranges > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (04:58:25): - Attachment: #671 hpAnnot > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/babelomics/hpAnnot > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:49:35):

2018-03-12

Unknown User (10:14:20): Unknown User (10:27:07): - Attachment: #672 MBttest > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Yuande/MBttest > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-03-13

Unknown User (10:00:33):

2018-03-14

Unknown User (09:41:22): - Attachment: #673 tissueTreg > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/cimbusch/tissueTreg > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:18:24): - Attachment: #674 BioNetStat > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jardimViniciusC/BioNetStat > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-03-15

Unknown User (18:25:51): - Attachment: #675 ccfindR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hjunwoo/ccfindR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:50:58): Unknown User (18:50:59): Unknown User (18:51:00): Unknown User (18:51:02): Unknown User (18:51:03): Unknown User (18:51:05): Unknown User (18:51:06):

2018-03-16

Unknown User (14:27:19): - Attachment: #676 CytoDx: Robust Prediction of Clinical Outcomes Using Cytometry Data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hzc363/CytoDx > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-03-18

Unknown User (04:06:26): - Attachment: #677 ccfindR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hjunwoo/ccfindR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (04:06:28): Unknown User (20:15:45): - Attachment: #678 iSEE: Interactive SummarizedExperiment Explorer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/csoneson/iSEE > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-03-19

Unknown User (05:25:28): - Attachment: #679 InTAD > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/kokonech/InTAD > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (06:22:55): - Attachment: #680 missRows > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/GonzalezIgnacio/missRows > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (06:24:40): Unknown User (09:33:14): - Attachment: #681 MSstatsQCgui: A shiny app for longitudinal quality monitoring for proteomic experiments > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/eralpdogu/MSstatsQCgui > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:06:37): Unknown User (13:57:41): - Attachment: #682 seqsetvis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jrboyd/seqsetvis > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:09:57): Unknown User (18:09:58):

2018-03-20

Unknown User (00:18:33): - Attachment: #683 mlmm package written for multivariate linear model for data with missing and censored respondents > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ireneslzeng/mlmm > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (00:18:34): Unknown User (09:46:21): - Attachment: #684 Rmmquant > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/mzytnicki/Rmmquant > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:32:24): Unknown User (13:32:25): Unknown User (13:32:26): Unknown User (16:54:22): - Attachment: #685 SeSAMe > Hello, > I’d like to contribute the SeSAMe package to bioconductor. It’s my first attempt of a bioconductor submission. Let me know what I am missing. Thank you! > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/zwdzwd/sesame > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-03-23

Unknown User (10:20:16): - Attachment: #686 MBttest > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Yuande/MBttest > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor [Package Submission][2] > instructions. My package is consistent with the Bioconductor > [Package Guidelines][1]. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the [support site][3] for issues that users may > have, subscribing to the [bioc-devel][4] mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using [Git][5] > (optionally [via GitHub][6]).

Unknown User (10:20:17):

2018-03-24

Unknown User (22:39:37): - Attachment: #687 rWikiPathways > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wikipathways/rwikipathways > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-03-25

Unknown User (23:52:46): - Attachment: #688 Requesting new bioconductor submission called Ularcirc (a shiny app) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/VCCRI/Ularcirc > > Confirm the following by editing each check box to ‘[x]’ > > • [ x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x ] The ‘devel’ branch for new packages and features. > • [ x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-03-26

Unknown User (01:31:31): - Attachment: #689 A package written for mass-spec data with abundant-dependent missing and censored values > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ireneslzeng/mlmm > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (06:13:15): - Attachment: #690 hipathia > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/babelomics/hipathia > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-03-27

Unknown User (11:26:40): Unknown User (11:35:38): Unknown User (11:50:17): - Attachment: #691 rWikiPathways > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:50:18): Unknown User (11:51:18): - Attachment: #692 rWikiPathways > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wikipathways/rWikiPathways > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:27:25): Unknown User (16:27:26): Unknown User (17:43:46): Unknown User (18:50:08): - Attachment: #693 SparseSignatures > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/danro9685/SparseSignatures > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-03-28

Unknown User (10:50:17): Unknown User (10:51:51): Unknown User (10:52:24): Unknown User (11:39:41): Unknown User (11:39:43):

2018-03-29

Unknown User (08:15:14): - Attachment: #694 new submission of GSLA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:15:15): Unknown User (08:54:23): - Attachment: #695 ASICS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/GaelleLefort/ASICS > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:34:49): - Attachment: #696 Submitting new package “TissueEnrich” > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Tuteja-Lab/TissueEnrich > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:34:51): Unknown User (12:40:47): - Attachment: #697 Submitting New Package “TissueEnrich” > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Tuteja-Lab/TissueEnrich > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-03-30

Unknown User (04:22:05): - Attachment: #698 SIAMCAT > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/KonradZych/SIAMCAT > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:51:35): - Attachment: #699 singleCellTK > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/compbiomed/singleCellTK > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:05:48): - Attachment: #700 sevenC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ibn-salem/sevenC > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-03-31

Unknown User (15:01:05): - Attachment: #701 HDCytoData (ExperimentHub) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/lmweber/HDCytoData > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:01:06): Unknown User (15:04:00): - Attachment: #702 HDCytoData (ExperimentHub) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/lmweber/HDCytoData > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-04-01

Unknown User (18:15:33): - Attachment: #703 diffcyt > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/lmweber/diffcyt > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:17:15): - Attachment: #704 IGV > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/paul-shannon/IGV > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-04-02

Unknown User (09:53:54): Unknown User (11:27:53): - Attachment: #705 package TFutils submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/shwetagopaul92/TFutils > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:35:09): - Attachment: #706 modulaRmap > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jrybarczyk/modulaRmap > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:24:05): - Attachment: #707 FlowSorted.Blood.EPIC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/immunomethylomics/FlowSorted.Blood.EPIC > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:24:06): Unknown User (15:45:42): - Attachment: #708 contributing TxRegInfra > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/vjcitn/TxRegInfra > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:48:11): - Attachment: #709 submitting BiocOncoTK > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/vjcitn/BiocOncoTK > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:18:31): - Attachment: #710 FlowSorted.Blood.EPIC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/immunomethylomics/FlowSorted.Blood.EPIC > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:10:57): Unknown User (17:14:15): Unknown User (17:14:17): Unknown User (17:14:18):

2018-04-03

Unknown User (09:16:13): - Attachment: #711 BiocMetaWorkflow > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/grimbough/BiocMetaWorkflow > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:08:44): - Attachment: #712 mdp > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/csbl-usp/mdp/ > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-04-04

Unknown User (07:11:14): - Attachment: #713 sigFeature: an R-package for significant feature selection using SVM-RFE & t-statistic > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/pijush1285/sigFeature > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:42:39): - Attachment: #714 https://github.com/gitter-lab/LPWC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:42:40): Unknown User (11:45:22): - Attachment: #715 Lag Penalized Weighted Correlation > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/gitter-lab/LPWC > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (22:15:29): Unknown User (22:20:38): - Attachment: #716 SeSAMe > Hi, @vobencha , > This is the first submission of the data package for sesame. Per our discussion, I closed the previous issue of this package and resubmit the data package here first. I will submit the code package and post my response to your last review once the data package is approved. Thank you for your help! > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/zwdzwd/sesameData > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-04-05

Unknown User (18:33:40):

2018-04-06

Unknown User (13:08:50):

2018-04-08

Unknown User (07:56:21): - Attachment: #717 RandomWalkRestartMH > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/alberto-valdeolivas/RandomWalkRestartMH > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-04-09

Unknown User (09:57:37): Unknown User (13:06:11): Unknown User (13:06:12): Unknown User (13:06:13): Unknown User (13:06:14): Unknown User (13:06:15): Unknown User (13:06:16):

2018-04-10

Unknown User (09:16:07): Unknown User (10:29:51): - Attachment: #718 ORFik > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/JokingHero/ORFik > > Confirm the following by editing each check box to ‘[x]’ > > • [ x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x ] The ‘devel’ branch for new packages and features. > • [ x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:21:53): - Attachment: #719 icetea > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/vivekbhr/icetea > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:14:55): - Attachment: #720 GIGSEA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/zhushijia/GIGSEA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (22:47:43): - Attachment: #721 MetaGxPancreas > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bhklab/MetaGxPancreas > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-04-11

Unknown User (10:21:37): Unknown User (10:21:39): Unknown User (10:21:39): Unknown User (10:21:41): Unknown User (10:21:43): Unknown User (14:13:11):

2018-04-12

Unknown User (09:40:23): - Attachment: #722 maser > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/DiogoVeiga/maser > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-04-13

Unknown User (01:23:04): Unknown User (14:00:07): Unknown User (14:13:13): - Attachment: #723 igvR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/paul-shannon/igvR > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-04-14

Unknown User (01:38:01): - Attachment: #724 Hapi > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (01:38:02): Unknown User (01:39:17): - Attachment: #725 Hapi > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Jialab-UCR/Hapi > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:25:46): Unknown User (12:25:49): Unknown User (13:14:31): Unknown User (13:39:37): Unknown User (13:39:38): Unknown User (13:39:39): Unknown User (13:39:40): Unknown User (13:39:40): Unknown User (13:39:41): Unknown User (13:39:42): Unknown User (13:39:43): Unknown User (13:39:44): Unknown User (13:39:45):

2018-04-15

Unknown User (00:49:03): - Attachment: #726 CAMTHC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Lululuella/CAMTHC > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-04-16

Unknown User (13:50:05): Unknown User (13:50:06): Unknown User (13:50:07):

2018-04-17

Unknown User (09:50:05): - Attachment: #727 onlineFDR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/dsrobertson/onlineFDR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-04-18

Unknown User (07:18:58): - Attachment: #728 Unable to run plotCountDepth function > This is my data type > > str(sce.data.SCnorm) > > num [1:33694, 1:8594] 0 0 0 0 0 0 0 0 0 0 … > • attr(*, “dimnames”)=List of 2 > ..$ : chr [1:33694] “ENSG00000243485” “ENSG00000237613” “ENSG00000186092” “ENSG00000238009” … > ..$ : chr [1:8594] “AAACCTGAGAATCTCC-1” “AAACCTGAGAGCCTAG-1” “AAACCTGAGAGGACGG-1” “AAACCTGAGCGATAGC-1” … > I am applying “plotCountDepth(Data = sce.data.SCnorm, FilterCellProportion = .1)” on my 10x data but following error comes. > Error in ExprGroups[[x]] : subscript out of bounds > In addition: Warning message: > In max(DensH) : no non-missing arguments to max; returning -Inf > How could use SCnorm on my data?

Unknown User (07:18:59): Unknown User (14:16:06): Unknown User (17:56:39): Unknown User (17:56:40): Unknown User (17:56:41): Unknown User (17:56:41): Unknown User (17:56:42): Unknown User (17:56:43):

2018-04-19

Unknown User (11:01:53):

2018-04-20

Unknown User (02:46:38): - Attachment: #729 BioMedR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wind22zhu/BioMedR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (02:46:39): Unknown User (15:10:05): - Attachment: #730 GeneAccord > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/cbg-ethz/GeneAccord > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (23:48:24): - Attachment: #731 GSminer: An R package for generating gold standard applied in gene functional network inference > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ShadowFiendSF/GSminer > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-04-21

Unknown User (12:14:05):

2018-04-22

Unknown User (15:40:44): Unknown User (15:40:45): Unknown User (15:40:45):

2018-04-23

Unknown User (13:32:46): - Attachment: #732 epihet > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:32:47): Unknown User (13:38:27): - Attachment: #733 epihet > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/TheJacksonLaboratory/epihet.git > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:38:28): Unknown User (13:59:26): - Attachment: #734 qPLEXanalyzer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/crukci-bioinformatics/qPLEXanalyzer > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:59:28): Unknown User (14:08:37): - Attachment: #735 qPLEXanalyzer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/crukci-bioinformatics/qPLEXanalyzer > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:11:51): - Attachment: #736 epihet > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/TheJacksonLaboratory/epihet.git > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:11:52): Unknown User (17:12:47): - Attachment: #737 epihet > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/TheJacksonLaboratory/epihet.git > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:12:48): Unknown User (17:35:55): - Attachment: #738 epihet > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/TheJacksonLaboratory/epihet.git > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:35:56): Unknown User (17:39:36): - Attachment: #739 epihet > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/TheJacksonLaboratory/epihet > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-04-24

Unknown User (13:12:53): - Attachment: #740 sigFeature: Significant feature selection using SVM-RFE & t-statistic > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/pijush1285/sigFeature > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:12:55): Unknown User (14:23:11): Unknown User (14:23:15): Ju Yeong Kim (14:45:28): > @Ju Yeong Kim has left the channel

2018-04-25

Unknown User (09:47:09): Unknown User (09:47:10): Unknown User (09:47:11): Unknown User (09:56:54): Unknown User (16:09:22): Unknown User (16:50:01): - Attachment: #741 issue > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ressomlab/INDEED > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:55:35):

2018-04-26

Unknown User (04:24:25): Unknown User (04:24:26):

2018-04-27

Unknown User (00:47:36): - Attachment: #742 Submission of package”consensus” to Bioconductor > • Repository: https://github.com/timpeters82/consensus > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor [Package Submission][2] > instructions. My package is consistent with the Bioconductor > [Package Guidelines][1]. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the [support site][3] for issues that users may > have, subscribing to the [bioc-devel][4] mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using [Git][5] > (optionally [via GitHub][6]).

2018-04-30

Unknown User (02:42:27): - Attachment: #743 CellTrails > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/dcellwanger/CellTrails > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-05-01

Unknown User (08:15:35): - Attachment: #744 DEqMS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yafeng/DEqMS > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:15:37): Unknown User (13:39:25): - Attachment: #745 Iteratively Adjusted Surrogate Variable Analysis (IA-SVA) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/UcarLab/IA-SVA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:39:26): Unknown User (13:41:20): - Attachment: #746 Iteratively Adjusted Surrogate Variable Analysis (iasva) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/UcarLab/iasva > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-05-02

Unknown User (04:35:03): - Attachment: #747 new submission of GSLA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/shaojunyu/GSLA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (07:24:29): - Attachment: #748 DEqMS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yafeng/DEqMS > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:17:44): Unknown User (13:55:39): - Attachment: #749 gwasurvivr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/suchestoncampbelllab/gwasurvivr > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-05-03

Unknown User (05:27:49): - Attachment: #750 rat2302frmavecs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/vbelcastPM/rat2302frmavecs > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (07:34:56): - Attachment: #751 allenpvc > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/diogo-branco/allenpvc > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:34:14): - Attachment: #752 MetID > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ressomlab/MetID > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-05-04

Unknown User (16:40:39): Unknown User (19:59:36): - Attachment: #753 qckitfastq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/compbiocore/qckitfastq > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-05-08

Unknown User (14:47:01):

2018-05-09

Unknown User (10:58:11): Unknown User (11:44:33): Unknown User (16:53:30): Unknown User (18:36:12): - Attachment: #754 GREP2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/uc-bd2k/GREP2 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-05-10

Unknown User (19:34:53): - Attachment: #755 slingshot > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/kstreet13/slingshot > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-05-17

Unknown User (07:01:52): Unknown User (07:01:56): Unknown User (09:55:34): Unknown User (11:52:53):

2018-05-18

Unknown User (09:17:36):

2018-05-19

Unknown User (17:52:23): - Attachment: #756 scruff > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/compbiomed/scruff > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-05-21

Unknown User (13:16:11): Unknown User (16:25:36): - Attachment: #757 HPAanalyze > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/trannhatanh89/HPAanalyze > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-05-22

Unknown User (12:25:21): - Attachment: #758 methylGO > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/reese3928/methylGO > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-05-23

Unknown User (09:33:04):

2018-05-24

Unknown User (08:18:57): - Attachment: #759 ACE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/tgac-vumc/ACE > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:37:42):

2018-05-29

Unknown User (15:10:57): - Attachment: #760 brainImageR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/saralinker/brainImageR > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-05-30

Unknown User (13:19:56): Unknown User (13:19:58): Unknown User (13:19:59): Unknown User (13:20:00): Unknown User (13:20:01): Unknown User (13:23:07): Unknown User (13:43:04): Unknown User (13:43:09):

2018-05-31

Unknown User (17:19:27):

2018-06-02

Unknown User (10:20:03):

2018-06-04

Unknown User (19:43:32): - Attachment: #761 ERSSA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/zshao1/ERSSA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-06-05

Unknown User (11:41:05): - Attachment: #762 ExCluster > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/RMTbioinfo/ExCluster > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:05:07): Unknown User (13:05:20): Unknown User (13:22:47): - Attachment: #763 ExCluster > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/RMTbioinfo/ExCluster > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:22:48): Unknown User (15:07:06): Unknown User (15:07:16):

2018-06-06

Unknown User (10:35:35): - Attachment: #764 PkgA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/lshep/PkgA > > Confirm the following by editing each check box to ‘[x]’ > > • [ X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ X] The ‘devel’ branch for new packages and features. > • [ X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:37:42):

2018-06-07

Unknown User (14:09:35): Unknown User (14:10:21):

2018-06-08

Unknown User (05:02:11): - Attachment: #765 maEndToEnd workflow package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/b-klaus/maEndToEnd > > This package is a workflow > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:08:28): Unknown User (13:08:30):

2018-06-11

Unknown User (07:03:52): - Attachment: #766 MetNet submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/tnaake/MetNet > > Confirm the following by editing each check box to ‘[x]’ > > • [ x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x ] The ‘devel’ branch for new packages and features. > • [ x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:26:56): - Attachment: #767 updog > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/dcgerard/updog > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:06:36): - Attachment: #768 GIGSEAdata > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/zhushijia/GIGSEAdata.git > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:06:37): Unknown User (17:14:12): - Attachment: #769 GIGSEAdata > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/zhushijia/GIGSEAdata > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-06-12

Unknown User (07:00:00): Unknown User (09:36:20): - Attachment: #770 coRdon > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/BioinfoHR/coRdon > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-06-13

Unknown User (07:09:43): - Attachment: #771 condcomp > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (07:09:44): Unknown User (07:11:05): - Attachment: #772 condcomp > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/CostaLab/condcomp > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:55:06): - Attachment: #773 hierinf > • Repository: https://github.com/crbasel/hierinf > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-06-14

Unknown User (01:27:40): - Attachment: #774 strandCheckR > • Repository: https://github.com/UofABioinformaticsHub/strandCheckR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-06-19

Unknown User (10:05:17): - Attachment: #775 NBSplice > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/gamerino/NBSplice > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:45:44): Unknown User (17:45:45):

2018-06-20

Unknown User (05:13:49): - Attachment: #776 proposal new logo design contribution > Hi !! I shared some ideas about new logo for the project… > Let me know what do you think!! > > greetings > azcwgloazd9fsdrpqv57 > eywb4vjgoexqgc8m0boo > m42wppuys1uhxlrncigk > qg6n33aba0ake6zstjpy

Unknown User (05:13:50): Unknown User (05:17:00): - Attachment: #777 New logo design proposal contribution > https://github.com/0relmely > > Hi !! I shared some ideas about new logo for the project… > Let me know what do you think!! > > greetings > azcwgloazd9fsdrpqv57 > eywb4vjgoexqgc8m0boo > m42wppuys1uhxlrncigk > qg6n33aba0ake6zstjpy

Unknown User (05:17:00): Unknown User (05:19:05): - Attachment: #778 Proposal , new logo design contribution > https://github.com/0relmely/reponame > > Hi !! I shared some ideas about new logo for the project… > Let me know what do you think!! > > greetings > azcwgloazd9fsdrpqv57 > eywb4vjgoexqgc8m0boo > m42wppuys1uhxlrncigk > qg6n33aba0ake6zstjpy

Unknown User (05:19:05): Unknown User (16:38:23):

2018-06-21

Unknown User (12:05:08): - Attachment: #779 NutrienTrackeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/AndreaRMICL/NutrienTrackeR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:43:50): Unknown User (13:43:37): Unknown User (13:47:00): Unknown User (13:47:01):

2018-06-24

Unknown User (08:09:28): - Attachment: #780 kmknn > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/LTLA/kmknn > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-06-26

Unknown User (08:37:49): - Attachment: #781 BUScorrect > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/XiangyuLuo/BUScorrect > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:50:44): - Attachment: #782 OUTRIDER - OUTlier in RNA-Seq fInDER > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/gagneurlab/OUTRIDER > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:24:16):

2018-06-27

Unknown User (06:26:38): - Attachment: #783 ipdDb > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/DKMS-LSL/ipdDb > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:10:48): Unknown User (13:55:24): - Attachment: #784 SIMD > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/FocusPaka/SIMD-package > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:55:25): Unknown User (15:23:38): - Attachment: #785 Gimpute > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/transbioZI/Gimpute > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:33:09): - Attachment: #786 rnaseqDTU > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/mikelove/rnaseqDTU > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:01:38): Unknown User (19:54:24): - Attachment: #787 LRBaseDbi > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/rikenbit/LRBaseDbi > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-06-28

Unknown User (02:51:56): - Attachment: #788 SIMD > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/FocusPaka/SIMD > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (07:47:25): - Attachment: #789 appreci8R > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/sandmanns/appreci8R > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:09:19): - Attachment: #790 SIMD > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/FocusPaka/SIMD > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:09:20): Unknown User (13:12:44): - Attachment: #791 LoomExperiment > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor/LoomExperiment > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-06-29

Unknown User (17:23:23): Unknown User (17:41:50): Unknown User (21:50:35): - Attachment: #792 ProteoMM: Model-Based Peptide-Level Analysis Platform for Combined Analysis of Multiple Omics Datasets > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/YuliyaLab/ProteoMM > Confirm the following by editing each check box to ‘[x]’ > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-07-01

Unknown User (04:37:52): - Attachment: #793 Epimethex: A tool for large-scale integrated analysis in methylation hotspots linked to genetic regulation. > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/giupardeb/EpiMethEx > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (04:37:52): Unknown User (04:48:16): - Attachment: #794 EpiMethEx: A tool for large-scale integrated analysis in methylation hotspots linked to genetic regulation. > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/giupardeb/EpiMethEx > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:31:00):

2018-07-03

Unknown User (10:21:09): Unknown User (11:53:28):

2018-07-04

Unknown User (10:37:46): - Attachment: #795 BDMMA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:37:46):

2018-07-05

Unknown User (09:53:51): - Attachment: #796 EpiMethEx: A tool for large-scale integrated analysis in methylation hotspots linked to genetic regulation. > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/giupardeb/EpiMethEx > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:53:52): Unknown User (10:18:52): Unknown User (10:18:53): Unknown User (10:18:54):

2018-07-10

Unknown User (12:50:34): - Attachment: #797 SeeGEM package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/davemcg/see_gem > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:50:36): Unknown User (12:58:07): - Attachment: #798 SeeGEM package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/davemcg/SeeGEM > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-07-11

Unknown User (19:13:22):

2018-07-12

Unknown User (04:11:54): - Attachment: #799 FoldGO > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/DanWiebe/FoldGO > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (04:33:00): Unknown User (10:43:48): - Attachment: #800 IsoCorrectoR: Correction Algorithm For Natural Isotope Abundance Contribution > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/chkohler/IsoCorrectoR > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:53:11): - Attachment: #801 HiCcompare2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jstansfield0/HiCcompare2 > > Confirm the following by editing each check box to ‘[x]’ > > • [ X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X ] The ‘devel’ branch for new packages and features. > • [X ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:42:00): - Attachment: #802 REBET > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wheelerb/REBET > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:31:34): - Attachment: #803 EnhancedVolcano > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/kevinblighe/EnhancedVolcano > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-07-13

Unknown User (05:41:46): - Attachment: #804 CopyNeutralIMA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/xpastor/CopyNeutralIMA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:52:44): - Attachment: #805 mnem > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/cbg-ethz/mnem > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-07-16

Unknown User (05:14:53): - Attachment: #806 tximeta > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/mikelove/tximeta > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:43:32): Unknown User (09:44:30):

2018-07-17

Unknown User (11:23:31): Unknown User (14:02:50): - Attachment: #807 remove references to svn and update to git

Unknown User (15:15:53):

2018-07-18

Unknown User (04:09:20): - Attachment: #808 NormalyzerDE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ComputationalProteomics/NormalyzerDE > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-07-20

Unknown User (10:54:47): Unknown User (10:54:48): Unknown User (10:54:48): Unknown User (10:54:49): Unknown User (10:54:50): Unknown User (10:54:51):

2018-07-24

Unknown User (06:10:17): - Attachment: #809 BDMMA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/DAIZHENWEI/BDMMA/tree/master/BDMMA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (06:10:18): Unknown User (13:27:16): - Attachment: #810 SAFEclustering > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yycunc/SAFEclustering > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-07-25

Unknown User (10:29:40): - Attachment: #811 uniConSigPreCal > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wangxlab/uniConSigPreCal > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:05:44): - Attachment: #812 DeMixT > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wwylab/DeMixT/DeMixT_0.2/ > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:05:45): Unknown User (11:50:17): - Attachment: #813 DeMixT > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wwylab/DeMixT/tree/master/DeMixT_0.2 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:50:18): Unknown User (11:56:14): - Attachment: #814 DeMixT > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wwylab/DeMixT > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:11:25):

2018-07-26

Unknown User (22:28:40): - Attachment: #815 decompTumor2Sig > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/rmpiro/decompTumor2Sig.git > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > [There is one notable exception here: preliminary versions of the package are already online at > http://rmpiro.net/decompTumor2Sig/index.html > Therefore, I hope that you can except a different version (1.3) from what you usually ask for (0.99); > please let me know if this is out of the question, or whether it is possible. Thank you! > Apart from this major issue, I have only some minor NOTEs, that I can address if necessary.] > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > [I do get a WARNING, but only due to the version number, see above. If I absolutely need to reset to version 0.99, then I’ll have to do so, but I’d prefer not.] > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > [Not an expert here, though :-)] > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (22:28:41): Unknown User (22:37:31): - Attachment: #816 decompTumor2Sig > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/rmpiro/decompTumor2Sig > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > [There is one notable exception here: preliminary versions of the package are already online at > http://rmpiro.net/decompTumor2Sig/index.html > Therefore, I hope that you can except a different version (1.3) from what you usually ask for (0.99); > please let me know if this is out of the question, or whether it is possible. Thank you! > Apart from this major issue, I have only some minor NOTEs, that I can address if necessary.] > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > [Not an expert here, though :-)] > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-07-27

Unknown User (03:39:54): - Attachment: #817 primirTSS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ipumin/primirTSS > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:40:31): - Attachment: #818 primirTSS(fixed the error) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ipumin/primirTSS > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:40:32):

2018-07-28

Unknown User (09:47:36): Unknown User (09:53:06): - Attachment: #819 uniConSigPreCal > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wangxlab/uniConSigPreCal > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:53:06): Unknown User (10:02:37): - Attachment: #820 uniConSig > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wangxlab/uniConSig > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:02:38): Unknown User (10:22:17): - Attachment: #821 uniConSig > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wangxlab/uniConSig > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-07-29

Unknown User (18:45:56): - Attachment: #822 NeighborNet > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/saharansari/NeighborNet > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-07-31

Unknown User (01:42:28): - Attachment: #823 Package Submission (nuCpos) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hkatomed/nuCpos > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (01:42:30): Unknown User (02:10:50): - Attachment: #824 nuCpos > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hkatomed/nuCpos > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (03:44:27): Unknown User (03:45:53):

2018-08-01

Unknown User (06:46:12):

2018-08-03

Unknown User (09:26:29): - Attachment: #825 miRSM > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/zhangjunpeng411/miRSM > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:35:40): Unknown User (11:45:05):

2018-08-04

Unknown User (13:22:53): - Attachment: #826 BioSeurat > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/kevinrue/BioSeurat > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (22:19:04): - Attachment: #827 celaref > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/MonashBioinformaticsPlatform/celarefData > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-08-05

Unknown User (08:42:51):

2018-08-06

Unknown User (10:23:16): Unknown User (10:23:17): Unknown User (10:23:18): Unknown User (10:23:19): Unknown User (10:23:20): Unknown User (10:23:21): Unknown User (10:24:13): Unknown User (14:48:29): - Attachment: #828 SmCCNet > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/KechrisLab/SmCCNet > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-08-07

Unknown User (03:45:27): - Attachment: #829 MPRAnalyze > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/YosefLab/MPRAnalyze > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:33:20): - Attachment: #830 PhysioSpaceMethods > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/JRC-COMBINE/PhysioSpaceMethods > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-08-08

Unknown User (09:01:29): - Attachment: #831 mcsurvdata > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/adricaba/mcsurvdata > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (19:50:11): - Attachment: #832 breakpointR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/daewoooo/BreakPointR > • AdditionalPackage: https://github.com/daewoooo/strandseqExampleData > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (19:50:12): Unknown User (20:31:19): - Attachment: #833 sparsenetgls > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (20:35:04): - Attachment: #834 sparsenetgls > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/superOmics/sparsenetgls > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (20:43:07):

2018-08-09

Unknown User (17:15:10): - Attachment: #835 breakpointRdata > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/daewoooo/breakpointRdata > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-08-10

Unknown User (05:13:34): Unknown User (05:13:38): Unknown User (17:10:18):

2018-08-15

Unknown User (15:08:38): - Attachment: #836 Batch effect correction for microbiome data with Bayesian Dirichlet-multinomial regression > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:08:39): Unknown User (15:11:04): - Attachment: #837 Batch effect correction for microbiome data with Bayesian Dirichlet-multinomial regression > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/DAIZHENWEI/BDMMAcorrect > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:11:04): Unknown User (15:14:42): - Attachment: #838 Batch effect correction for microbiome data with Bayesian Dirichlet-multinomial regression > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/DAIZHENWEI/BDMMA > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:14:46): Unknown User (15:21:49): - Attachment: #839 Batch effect correction for microbiome data with Bayesian Dirichlet-multinomial regression > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/DAIZHENWEI/BDMMAcorrect > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-08-16

Unknown User (05:50:13): - Attachment: #840 DuoClustering2018 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/csoneson/DuoClustering2018 > > cc @csoneson > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:57:21): - Attachment: #841 SCBN > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/FocusPaka/SCBN > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-08-17

Unknown User (10:33:05): Unknown User (10:33:06): Unknown User (10:33:07): Unknown User (12:44:47): - Attachment: #842 tispec > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/roonysgalbi/tispec > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:18:13): Unknown User (16:10:46): - Attachment: #843 brainimageRdata > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/saralinker/brainimageRdata > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-08-18

Unknown User (10:06:23):

2018-08-20

Unknown User (10:45:06): - Attachment: #844 An R package for quantitative integration and analysis of multiple omics assays from heterogeneous samples > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/subhadeep1024/OMICsPCA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:47:02): - Attachment: #845 Supporting data for package OMICsPCA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/subhadeep1024/OMICsPCAdata > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:35:53): Unknown User (13:08:53): - Attachment: #846 XINA > Hello, > > I am Lang and want to submit XINA to Bioconductor. I checked XINA by using R CMD Check and Bioccheck and found no warnings and no errors. Of course, I know these are just minimum requirements. Please consider XINA to add to the Bioconductor repository. I attached the abstract part of XINA manuscript that I submitted to Journal of Proteome Research. > > XINA ABSTRACT > Quantitative proteomics experiments, using for instance isobaric tandem mass tagging approaches, are conducive to measuring changes in protein abundance over multiple time points in response to one or more conditions or stimulations. The aim is often to determine which proteins exhibit similar patterns within and across experimental conditions, since proteins with co-abundance patterns may have common molecular functions related to a given stimulation. In order to facilitate identification and analyses of co-abundance patterns within and across conditions, we previously developed a software inspired by the isobaric mass tagging method itself. Specifically, multiple datasets are tagged in silico and combined for subsequent subgrouping into multiple clusters within a single output depicting the variation across all conditions; converting a typical inter-dataset comparison into an intra-dataset comparison. An updated version of our software, XINA, not only extracts co-abundance profiles within and across experiments, but also incorporates protein-protein interaction databases and integrative resources such as KEGG to infer interactors and molecular functions, respectively, and produces user-friendly graphical outputs. In this report we compare the kinetics profiles of >5,600 unique proteins derived from three macrophage cell culture experiments and demonstrate through intuitive visualizations that XINA identifies key regulators of macrophage activation via their co-abundance patterns. > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/langholee/XINA > > Confirm the following by editing each check box to ‘[x]’ > > • [O] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [O] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [O] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [O] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [O] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [O] The ‘devel’ branch for new packages and features. > • [O] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [O] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:08:54): Unknown User (13:38:53): - Attachment: #847 XINA: a workflow for the integration of multiplexed proteomics kinetics data with network analysis > Hello, > > I am Lang and want to submit XINA to Bioconductor. I checked XINA by using R CMD Check and Bioccheck and found no warnings and no errors. Of course, I know these are just minimum requirements. Please consider XINA to add to the Bioconductor repository. I attached the abstract part of XINA manuscript that I submitted to Journal of Proteome Research. > > XINA ABSTRACT > Quantitative proteomics experiments, using for instance isobaric tandem mass tagging approaches, are conducive to measuring changes in protein abundance over multiple time points in response to one or more conditions or stimulations. The aim is often to determine which proteins exhibit similar patterns within and across experimental conditions, since proteins with co-abundance patterns may have common molecular functions related to a given stimulation. In order to facilitate identification and analyses of co-abundance patterns within and across conditions, we previously developed a software inspired by the isobaric mass tagging method itself. Specifically, multiple datasets are tagged in silico and combined for subsequent subgrouping into multiple clusters within a single output depicting the variation across all conditions; converting a typical inter-dataset comparison into an intra-dataset comparison. An updated version of our software, XINA, not only extracts co-abundance profiles within and across experiments, but also incorporates protein-protein interaction databases and integrative resources such as KEGG to infer interactors and molecular functions, respectively, and produces user-friendly graphical outputs. In this report we compare the kinetics profiles of >5,600 unique proteins derived from three macrophage cell culture experiments and demonstrate through intuitive visualizations that XINA identifies key regulators of macrophage activation via their co-abundance patterns. > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > Repository: https://github.com/langholee/XINA > Confirm the following by editing each check box to ‘[x]’ > > [O] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > [O] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > [O] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > [O] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > [O] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > [O] The ‘devel’ branch for new packages and features. > [O] The stable ‘release’ branch, made available every six > months, for bug fixes. > [O] Bioconductor version control using Git > (optionally via GitHub). > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:48:53): - Attachment: #848 artMS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/biodavidjm/artMS > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-08-21

Unknown User (14:37:21): Unknown User (14:37:22):

2018-08-24

Unknown User (09:59:08): Unknown User (09:59:09): Unknown User (09:59:09): Unknown User (09:59:11): Unknown User (14:07:14): - Attachment: #849 glmSparseNet > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/sysbiomed/glmSparseNet > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:29:29): - Attachment: #850 plotGrouper > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jdgagnon/plotGrouper > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:29:30): Unknown User (18:32:06): - Attachment: #851 plotGrouper > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jdgagnon/plotGrouper/tree/master/pkg > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:32:06): Unknown User (18:39:31): - Attachment: #852 plotGrouper > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jdgagnon/plotGrouper > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-08-25

Unknown User (18:18:02): - Attachment: #853 DeMixT > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wwylab/DeMixT > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:18:03):

2018-08-27

Unknown User (11:35:26):

2018-08-28

Unknown User (20:41:02): - Attachment: #854 BiocPkgTools > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/seandavi/BiocPkgTools > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-08-29

Unknown User (21:37:53): - Attachment: #855 TENxPBMCData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/kasperdanielhansen/TENxPBMCData > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (23:35:20): Unknown User (23:35:21): Unknown User (23:35:22):

2018-08-30

Unknown User (13:18:37): - Attachment: #856 HiCLegos > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/koustav-pal/HiCLegos > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:09:11): - Attachment: #857 AssessORF > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/DRK248/AssessORF > • AdditionalPackage: https://github.com/DRK248/AssessORFData > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:09:13): Unknown User (18:12:53): - Attachment: #858 AssessORF > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/DRK248/AssessORF > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-08-31

Unknown User (08:17:16): - Attachment: #859 TabulaMurisData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/csoneson/TabulaMurisData > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-09-04

Unknown User (11:41:04): - Attachment: #860 AffiXcan > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/alussana/AffiXcan > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:38:48):

2018-09-05

Unknown User (12:32:16):

2018-09-06

Unknown User (16:26:28): - Attachment: #861 DelayedDataFrame > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor/DelayedDataFrame > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:46:47): - Attachment: #862 VariantExperiment > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor/VariantExperiment > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-09-07

Unknown User (15:12:46): Unknown User (15:12:46): Unknown User (15:12:47): Unknown User (16:46:36): Unknown User (16:59:51):

2018-09-09

Unknown User (08:25:14):

2018-09-11

Unknown User (12:18:27): Unknown User (12:18:29): Unknown User (12:18:29):

2018-09-12

Unknown User (03:52:52): - Attachment: #863 3532135321 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (03:52:52): Unknown User (06:40:50): - Attachment: #864 HIREewas > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/XiangyuLuo/HIREewas > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:48:43): - Attachment: #865 PCRSA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/databio/PCRSA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-09-13

Unknown User (08:34:30): - Attachment: #866 gpart > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/sunnyeesl/gpart > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-09-14

Unknown User (04:02:37): - Attachment: #867 IsoCorrectoRGUI: A Graphical User Interface for IsoCorrectoR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/chkohler/IsoCorrectoRGUI > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (06:00:24): - Attachment: #868 QSutils > • Repository: https://github.com/VHIRHepatiques/QSutils > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor [Package Submission][2] > instructions. My package is consistent with the Bioconductor > [Package Guidelines][1]. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the [support site][3] for issues that users may > have, subscribing to the [bioc-devel][4] mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using [Git][5] > (optionally [via GitHub][6]).

Unknown User (11:46:15): Unknown User (11:46:16): Unknown User (11:46:17): Unknown User (12:28:03): - Attachment: #869 tcgaWGBSData.hg19 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/aryeelab/tcgaWGBSData.hg19 > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-09-18

Unknown User (04:19:08): - Attachment: #870 https://github.com/JohnMengChun/ceRNAmiRNAfun > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (04:19:09): Unknown User (04:22:12): - Attachment: #871 https://github.com/JohnMengChun/ceRNAmiRNAfun > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (04:22:13): Unknown User (04:24:05): - Attachment: #872 https://github.com/JohnMengChun/ceRNAmiRNAfun > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (04:24:06): Unknown User (10:56:58): - Attachment: #873 deco > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:56:59): Unknown User (11:09:04): - Attachment: #874 https://github.com/JohnMengChun/ceRNAmiRNAfun > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:09:08): Unknown User (11:13:46): - Attachment: #875 https://github.com/JohnMengChun/ceRNAmiRNAfun > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/JohnMengChun/ceRNAmiRNAfun > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (23:03:33): - Attachment: #876 transite > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/kkrismer/transite > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-09-19

Unknown User (04:46:01): - Attachment: #877 PepsNMRData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ManonMartin/PepsNMRData > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (04:46:14):

2018-09-20

Unknown User (04:00:25): Unknown User (04:09:58): - Attachment: #878 bayNorm > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/WT215/bayNorm > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (06:40:53): Unknown User (22:49:49): - Attachment: #879 new package contribution > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/awaardenberg/KinSwingR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-09-21

Unknown User (11:29:12): - Attachment: #880 SpatialCPie > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jbergenstrahle/SpatialCPie > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:21:14): - Attachment: #881 RNASeqR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/HowardChao/RNASeqR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-09-22

Unknown User (23:14:46): - Attachment: #882 MSstatsTMT > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Vitek-Lab/MSstatsTMT > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-09-24

Unknown User (08:59:25): - Attachment: #883 cardelino > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/PMBio/cardelino > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-09-26

Unknown User (05:22:38): - Attachment: #884 scTensor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/rikenbit/scTensor > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:27:00): Unknown User (13:27:53): Unknown User (13:28:06): Unknown User (13:28:25): Unknown User (14:32:09): - Attachment: #885 cicero > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/cole-trapnell-lab/cicero-release > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:32:17): Unknown User (16:40:12): - Attachment: #886 cicero > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/cole-trapnell-lab/cicero > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-09-27

Unknown User (14:18:24): - Attachment: #887 tRNA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/FelixErnst/tRNA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-09-28

Unknown User (01:34:08): - Attachment: #888 consensusDE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/awaardenberg/consensusDE > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:20:12): - Attachment: #889 countsimQC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/csoneson/countsimQC > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:10:47): Unknown User (15:10:48): Unknown User (15:10:49): Unknown User (15:10:49): Unknown User (15:10:50): Unknown User (15:10:51): Unknown User (15:10:53): Unknown User (15:10:54): Unknown User (16:17:41): - Attachment: #890 RegParallel > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/kevinblighe/RegParallel > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-10-01

Unknown User (15:32:37): - Attachment: #891 PrecisionTrialDrawer submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/gmelloni/PrecisionTrialDrawer > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:51:04): - Attachment: #892 FCBF > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/lubianat/FCBF > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-10-02

Unknown User (11:12:16): - Attachment: #893 EuPathDB > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/elsayed-lab/EuPathDB > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:58:42): - Attachment: #894 epihet package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/TheJacksonLaboratory/epihet > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:58:43):

2018-10-03

Unknown User (12:30:39): - Attachment: #895 submit treeAGG package > • Repository: https://github.com/markrobinsonuzh/treeAGG.git > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:30:40): Unknown User (12:32:26): Unknown User (12:58:41): - Attachment: #896 submit package treeAGG > • Repository: https://github.com/markrobinsonuzh/treeAGG > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:43:08): - Attachment: #897 New package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wschen/phemd > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:30:13): Unknown User (17:34:52): Unknown User (20:54:20): - Attachment: #898 mixOmics > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/mixOmicsTeam/mixOmics > Please note that we have 3 branches. > • Master is the current mixOmics package on CRAN. > • Devel is the version in development > • BioC is the branch we are submitting to Bioconductor > > > mixOmics has been on CRAN since 2009 and we finally decided to convert to bioC. It is a big move for us and we are aware that our current submission needs further improvements. We hope to be able to stage some of our developments gradually. The future improvements we envisage in particular are to set up setGeneric and setMethods functions to fit in MultiAssayExperiments. We have not been successful so far and we need more time. > > We hope that mixOmics will benefit the bioC community and attract more users! You can see our engagement and commitment with the computational biology community at www.mixOmics.org > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [see below] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > Please note the following: > • R CMD check –as-cran gives 3 NOTES, all OK for bioconductor > • R CMD BiocCheck gives: > • 1 ERROR (remove package from CRAN as our package still needs to be live on CRAN > • 1 WARNING: that we cannot address because it’s relative to when we use the cpus argument in some of our functions, let me know if there is a work around this > • 4 NOTES: those include unit tests and aesthetics of the code. Our package includes > 100 R functions and we are unsure how to implement the unit tests at this stage. We welcome any feedback from you. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > > Yes! see www.mixOmics.org, mixOmics is an R toolkit for omics data integration. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (20:54:21): Unknown User (21:04:17): - Attachment: #899 mixOmics > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/mixOmicsTeam/mixOmics/tree/BioC/mixOmics > Please note that we have 3 branches. > • Master is the current mixOmics package on CRAN. > • Devel is the version in development > • BioC is the branch we are submitting to Bioconductor > > mixOmics has been on CRAN since 2009 and we finally decided to convert to bioC. It is a big move for us and we are aware that our current submission needs further improvements. We hope to be able to stage some of our developments gradually. The future improvements we envisage in particular are to set up setGeneric and setMethods functions to fit in MultiAssayExperiments. We have not been successful so far and we need more time. > We hope that mixOmics will benefit the bioC community and attract more users! You can see our engagement and commitment with the computational biology community at www.mixOmics.org > > Confirm the following by editing each check box to ‘[x]’ > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [see below] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > R CMD check –as-cran gives 3 NOTES, all OK for bioconductor > R CMD BiocCheck gives: > • 1 ERROR (remove package from CRAN as our package still needs to be live on CRAN > • 1 WARNING: that we cannot address because it’s relative to when we use the cpus argument in some of our functions, let me know if there is a work around this > • 4 NOTES: those include unit tests and aesthetics of the code. Our package includes > 100 R functions and we are unsure how to implement the unit tests at this stage. We welcome any feedback from you. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > Yes! see www.mixOmics.org, mixOmics is an R toolkit for omics data integration. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (21:04:18): Unknown User (21:35:25): - Attachment: #900 mixOmics > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/mixOmicsTeam/mixOmics > > > mixOmics has been on CRAN since 2009 and we finally decided to convert to bioC. It is a big move for us and we are aware that our current submission needs further improvements. We hope to be able to stage some of our developments gradually. The future improvements we envisage in particular are to set up setGeneric and setMethods functions to fit in MultiAssayExperiments. We have not been successful so far and we need more time. > > We hope that mixOmics will benefit the bioC community and attract more users! You can see our engagement and commitment with the computational biology community at www.mixOmics.org > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [see below] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > > Please note the following: > > • R CMD check –as-cran gives 3 NOTES, all OK for bioconductor > > • R CMD BiocCheck gives: > > • 1 ERROR (remove package from CRAN as our package still needs to be live on CRAN > > • 1 WARNING: that we cannot address because it’s relative to when we use the cpus argument in some of our functions, let me know if there is a work around this > > • 4 NOTES: those include unit tests and aesthetics of the code. Our package includes > 100 R functions and we are unsure how to implement the unit tests at this stage. We welcome any feedback from you. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-10-04

Levi Waldron (12:37:01): > @Levi Waldron has left the channel

Unknown User (15:08:13): - Attachment: #901 levi > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jrybarczyk/levi > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (19:15:02): - Attachment: #902 MMAPPR2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/kjohnsen/MMAPPR2 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (20:31:00): - Attachment: #903 universalmotif > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bjmt/universalmotif > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-10-05

Unknown User (02:16:18): - Attachment: #904 vistimeseq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/nlhuong/vistimeseq > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (04:28:07): - Attachment: #905 abseqR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/malhamdoosh/abseqR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:30:38): - Attachment: #906 cTRAP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/nuno-agostinho/cTRAP > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:58:57): - Attachment: #907 TeMPO > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/MalteThodberg/TeMPO > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:22:00): - Attachment: #908 ADAM > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jrybarczyk/ADAM > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:21:04): - Attachment: #909 Wrench > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/HCBravoLab/Wrench > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:46:32): - Attachment: #910 Celda Submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/compbiomed/celda > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (20:23:52): - Attachment: #911 MTseekerData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/trichelab/MTseekerData > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (21:09:14): - Attachment: #912 nanotatoR: next generation structural variant annotation and classification > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/VilainLab/Nanotator > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (21:09:15): Unknown User (21:20:50): - Attachment: #913 nanotatoR: next generation structural variant annotation and classification > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/VilainLab/nanotatoR > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (21:45:35): - Attachment: #914 compartmap > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/trichelab/compartmap > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (23:33:54): - Attachment: #915 ATACseeker > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/trichelab/ATACseeker > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-10-08

Unknown User (10:21:34): - Attachment: #916 replace outdated references to Subversion > This seems to be the last refuge of SVN in BioC…

2018-10-09

Unknown User (11:53:48): Unknown User (11:53:49): Unknown User (11:53:51): Unknown User (11:53:52): Unknown User (11:53:53): Unknown User (15:15:31): Unknown User (15:15:31):

2018-10-10

Unknown User (14:04:34):

2018-10-11

Unknown User (07:41:27):

2018-10-13

Unknown User (15:35:34): Unknown User (15:35:35): Unknown User (15:35:36): Unknown User (15:35:37): Unknown User (15:35:38):

2018-10-16

Unknown User (07:38:33): Unknown User (07:39:06): Unknown User (07:41:45): Unknown User (11:04:10): - Attachment: #917 DNABarcodeCompatibility > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/comoto-pasteur-fr/DNABarcodeCompatibility > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-10-17

Unknown User (11:31:52): - Attachment: #918 VCFArray > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor/VCFArray > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:44:36): - Attachment: #919 mms2plot > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:44:37):

2018-10-18

Unknown User (09:31:46): Unknown User (09:31:47): Unknown User (09:31:49): Unknown User (09:31:50): Unknown User (09:31:51): Unknown User (09:31:53): Unknown User (09:31:54): Unknown User (19:02:57): - Attachment: #920 AdductomicsR package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/JosieLHayes/adductomicsR > • Associated data repository (too large to put on Github): https://berkeley.box.com/s/titfjzlwhqmmjjwm9pw9uqv3ahpzotxm > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-10-19

Unknown User (17:27:46): - Attachment: #921 COCOA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/databio/COCOA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-10-20

Unknown User (18:02:08):

2018-10-21

Unknown User (19:33:11): Unknown User (22:20:57): - Attachment: #922 cytofast > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/KoenAStam/cytofast > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-10-22

Unknown User (15:17:27): Unknown User (15:18:25): Unknown User (15:18:25): Unknown User (15:18:25):

2018-10-23

Unknown User (12:08:47): Unknown User (12:08:49): Unknown User (12:08:49): Unknown User (15:09:06): Unknown User (15:09:08):

2018-10-24

Unknown User (12:58:57): Unknown User (12:58:59): Unknown User (13:00:24): Unknown User (13:25:57):

2018-10-25

Unknown User (13:26:30): Unknown User (15:32:52):

2018-10-26

Unknown User (06:52:27):

2018-10-27

Unknown User (14:12:31):

2018-10-29

Unknown User (12:11:14): - Attachment: #923 ComStat > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/gzrrobert/ComStat > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:38:12): Unknown User (15:32:00): Unknown User (15:32:01):

2018-10-30

Unknown User (10:38:34): Unknown User (10:38:36): Unknown User (10:38:37): Unknown User (10:38:39): Unknown User (10:38:40): Unknown User (14:20:25): - Attachment: #924 Missing Value Estimation of DNA Methylation Data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/pdilena/methyLImp > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-10-31

Unknown User (13:28:14): - Attachment: #925 epihet > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:28:14):

2018-11-02

Unknown User (12:20:32): - Attachment: #926 RRHO2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/RRHO2/RRHO2 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-11-05

Unknown User (07:32:45): - Attachment: #927 epihet > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (07:32:46): Unknown User (10:53:58):

2018-11-06

Charlotte Soneson (07:26:01): > @Charlotte Soneson has left the channel

Unknown User (09:54:20): - Attachment: #928 submission a new R package mms2plot > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/lileir/mms2plot > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-11-07

Unknown User (07:05:55): - Attachment: #929 deco > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/fjcamlab/deco > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:48:25): - Attachment: #930 graper > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bv2/graper > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:33:58): - Attachment: #931 NestLink (package type - Experiment Data ) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/cpanse/NestLink > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic and mass spectromety data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:21:42):

2018-11-08

Unknown User (10:48:30):

2018-11-09

Unknown User (10:43:48): - Attachment: #932 New Package Submission: GladiaTOX > • Repository: https://github.com/pmpsa-hpc/GladiaTOX > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor [Package Submission][2] > instructions. My package is consistent with the Bioconductor > [Package Guidelines][1]. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the [support site][3] for issues that users may > have, subscribing to the [bioc-devel][4] mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using [Git][5] > (optionally [via GitHub][6]).

2018-11-12

Unknown User (13:27:59): - Attachment: #933 CluMSIDdata > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/tdepke/CluMSIDdata > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-11-13

Unknown User (00:53:41): - Attachment: #934 PhosMap: A modular analysis R package for quantitative phosphoproteomics data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (00:53:42): Unknown User (03:21:38): - Attachment: #935 PhosMap > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ecnuzdd/PhosMap > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:27:14): - Attachment: #936 rScudo > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Matteo-Ciciani/rScudo > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-11-15

Unknown User (16:36:53): - Attachment: #937 HCAData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/federicomarini/HCAData > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-11-20

Unknown User (08:24:30): Unknown User (10:30:17): Unknown User (10:30:38): Unknown User (11:39:04): Unknown User (11:54:05): Unknown User (11:54:06): Unknown User (11:54:07): Unknown User (11:54:09): Unknown User (17:15:33): - Attachment: #938 epihet > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:15:34):

2018-11-22

Unknown User (01:39:34): - Attachment: #939 bigPint > • Repository: https://github.com/lrutter/bigPint > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor [Package Submission][2] > instructions. My package is consistent with the Bioconductor > [Package Guidelines][1]. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the [support site][3] for issues that users may > have, subscribing to the [bioc-devel][4] mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using [Git][5] > (optionally [via GitHub][6]).

2018-11-26

Unknown User (04:39:23): - Attachment: #940 SelfE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Priyadarshini-Rai/SelfE > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (05:27:42): Unknown User (09:19:53): - Attachment: #941 cola > • Repository: https://github.com/jokergoo/cola > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-11-28

Unknown User (09:57:14): - Attachment: #942 NPA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/pmpsa-hpc/NPAModels.git > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:57:16): Unknown User (10:04:44): - Attachment: #943 NPA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/pmpsa-hpc/NPAModels > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-11-29

Unknown User (10:17:10): Unknown User (10:17:12): Unknown User (15:42:15): - Attachment: #944 https://github.com/wangxlab/uniConSig > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:42:17): Unknown User (15:45:59): - Attachment: #945 https://github.com/wangxlab/uniConSig > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:46:00): Unknown User (15:48:54): - Attachment: #946 uniCongSig R package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wangxlab/uniConSig > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:48:56):

2018-11-30

Unknown User (02:42:33): Unknown User (06:05:06): - Attachment: #947 GAPGOM (novel Gene Annotation Prediction and other GO Metrics) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Berghopper/GAPGOM > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (07:17:42):

2018-12-03

Unknown User (10:35:47): - Attachment: #948 pram > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/pliu55/pram > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-12-05

Unknown User (08:24:01):

2018-12-06

Unknown User (08:53:01): - Attachment: #949 RCM package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/CenterForStatistics-UGent/RCM/tree/master > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:47:45): - Attachment: #950 iPeak > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/annaBio/iPeak > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:47:46):

2018-12-09

Unknown User (12:39:36):

2018-12-11

Unknown User (10:38:29): - Attachment: #951 PCAtools > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/kevinblighe/PCAtools > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:17:54): Unknown User (18:17:55): Unknown User (18:17:56): Unknown User (18:17:57):

2018-12-12

Unknown User (08:09:21):

2018-12-13

Unknown User (03:52:00): - Attachment: #952 https://github.com/ecnuzdd/PhosMap > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (03:52:01): Unknown User (04:34:58): - Attachment: #953 A Comprehensive R Package For Analyzing Quantitative Phosphoproteomics Data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ecnuzdd/PhosMap > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (04:35:00): Unknown User (08:21:39): - Attachment: #954 PhosMap > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ecnuzdd/PhosMap > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:21:40): Unknown User (09:27:58): Unknown User (16:22:03): Unknown User (16:22:04):

2018-12-17

Unknown User (10:30:15):

2018-12-18

Unknown User (09:55:45):

2018-12-19

Unknown User (12:18:19): Unknown User (17:01:57): - Attachment: #955 VariantExperiment > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor/VariantExperiment > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:01:58): Unknown User (17:13:43): Unknown User (17:44:10): - Attachment: #956 PrInCE (predicting interactomes from co-elution data) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/fosterlab/PrInCE-R > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:44:11): Unknown User (17:52:24): - Attachment: #957 PrInCE (predicting interactomes from co-elution data) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/fosterlab/PrInCE > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-12-20

Unknown User (09:37:47): Unknown User (09:37:53): Unknown User (09:51:41): - Attachment: #958 proBatch submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/symbioticMe/proBatch/tree/Bioconductor_submission > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-12-24

Unknown User (14:56:17):

2018-12-28

Unknown User (23:13:34): - Attachment: #959 Submission of “topconfects” package to Bioconductor > Hello Bioconductor developers, > > I would like to submit my “topconfects” R package to Bioconductor. It implements a method described in this preprint on BioRXiv: https://www.biorxiv.org/content/early/2018/06/11/343145 > > One difficulty I’ve run into is that I was unable to install the development version of R 3.6 from http://r.research.att.com/, the web page says something about “make check FAILED”, and therefore I couldn’t install the bioconductor devel version. However I don’t think this package depends on anything likely to be updated in the latest version. > > • Repository: https://github.com/pfh/topconfects > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2018-12-29

Unknown User (17:33:16): - Attachment: #960 atSNP package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/sunyoungshin/atSNP > > Confirm the following by editing each check box to ‘[x]’ > > • [ X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-01-02

Unknown User (10:37:56): Unknown User (21:12:58): - Attachment: #961 chipseqDBData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/LTLA/chipseqDBData > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-01-03

Unknown User (13:24:47):

2019-01-05

Unknown User (08:29:53): - Attachment: #962 Modstrings > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/FelixErnst/Modstrings > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:47:19): - Attachment: #963 BioMM: Biological-informed Multi-stage Machine learning framework for phenotype prediction using omics data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/transbioZI/BioMM > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-01-07

Unknown User (08:47:33): - Attachment: #964 rMVP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/XiaoleiLiuBio/MVP/ > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:47:35): Unknown User (08:59:02): - Attachment: #965 rMVP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/XiaoleiLiuBio/rMVP > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:05:57): - Attachment: #966 CNVRanger: summarization and quantitative trait analysis of CNV ranges > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/waldronlab/CNVRanger > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:27:01):

2019-01-08

Unknown User (06:40:20): - Attachment: #967 artdeco > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/RaikOtto/artdeco > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:58:08): - Attachment: #968 Xeva : XEnograft Visualization & Analysis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bhklab/Xeva > > Confirm the following by editing each checkbox to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-01-09

Unknown User (01:18:13): - Attachment: #969 TENxhgmmBUS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/BUStools/TENxhgmmBUS > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-01-10

Unknown User (11:39:07):

2019-01-11

Unknown User (12:13:55): - Attachment: #970 PAIRADISE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hubentu/PAIRADISE > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:12:46):

2019-01-13

Unknown User (12:30:48): Unknown User (12:31:21): Unknown User (20:16:44): - Attachment: #971 OVESEG > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Lululuella/OVESEG > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-01-14

Unknown User (16:19:16):

2019-01-15

Unknown User (05:17:07): - Attachment: #972 DepecheR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/theorell/DepecheR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [xI have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (05:36:51): - Attachment: #973 rmelting > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/aravind-j/rmelting > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:36:24):

2019-01-16

Unknown User (06:12:28): - Attachment: #974 Hello @mtmorgan, > Hello @mtmorgan, > > Can you please comment on this warning I got? > > R CMD check exceeded 5 min requirement > > I look forward to hearing from you. > > Sunyoung > > *Originally posted by @sunyoungshin in https://github.com/Bioconductor/Contributions/issues/960#issuecomment-451936768*

Unknown User (06:12:31): Unknown User (10:12:57): - Attachment: #975 CoRegFlux > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/i3bionet/CoRegFlux > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:24:08): - Attachment: #976 mfBiclust > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jonalim/mfBiclust > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:23:59):

2019-01-17

Unknown User (07:03:27): Unknown User (10:59:34): - Attachment: #977 Rhisat2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/fmicompbio/Rhisat2 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-01-18

Unknown User (12:22:02):

2019-01-21

Unknown User (05:20:14): - Attachment: #978 csawUsersGuide > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/LTLA/csawUsersGuide > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-01-22

Unknown User (02:34:41): - Attachment: #979 sitePath > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wuaipinglab/sitePath > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:52:27): Unknown User (16:53:54): - Attachment: #980 Rcwl > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hubentu/Rcwl > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-01-23

Unknown User (09:22:11): Unknown User (23:36:56): - Attachment: #981 divergence > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wikum/divergence > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-01-24

Unknown User (11:55:07): Unknown User (17:45:21):

2019-01-25

Unknown User (12:36:47):

2019-01-26

Unknown User (17:52:21): - Attachment: #982 FlowSorted.CordBloodCombined.450k > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/immunomethylomics/FlowSorted.CordBloodCombined.450k > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-01-29

Unknown User (16:22:27): - Attachment: #983 oct4 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/mikelove/oct4 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:23:12): - Attachment: #984 macrophage > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/mikelove/macrophage > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-01-31

Unknown User (09:24:23):

2019-02-01

Unknown User (10:08:01): - Attachment: #985 ngsReports Submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/UofABioinformaticsHub/ngsReports > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:21:36): - Attachment: #986 hypeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/montilab/hypeR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:25:29): - Attachment: #987 alevinQC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/csoneson/alevinQC > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-02-04

Unknown User (09:26:43): - Attachment: #988 MOFA and MOFAdata > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: > https://github.com/bioFAM/MOFA/tree/master/MOFA > https://github.com/bioFAM/MOFA/tree/master/MOFAdata > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:26:45): Unknown User (09:34:20): - Attachment: #989 MOFA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bioFAM/MOFA/tree/master/MOFAdata > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:34:22):

2019-02-05

Unknown User (02:11:40): - Attachment: #990 survtype > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (02:11:41): Unknown User (02:14:14): - Attachment: #991 survtype > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/dongminjung/survtype > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:57:51): - Attachment: #992 doseR submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/WaltersLab/doseR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:24:31): - Attachment: #993 SMAD > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/zqzneptune/SMAD > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-02-06

Unknown User (00:37:39): - Attachment: #994 curatedAdipoRNA: A Curated RNA-Seq Dataset of MDI-induced Differentiated Adipocytes (3T3-L1) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/MahShaaban/curatedAdipoRNA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (07:25:44): - Attachment: #995 MOFAdata > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bioFAM/MOFAdata > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:03:08): - Attachment: #996 BiocSingular > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/LTLA/BiocSingular > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:26:24): - Attachment: #997 ADAMgui > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jrybarczyk/ADAMgui > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:42:47): Unknown User (13:42:48): Unknown User (13:42:50): Unknown User (13:42:51): Unknown User (13:42:53):

2019-02-07

Unknown User (00:12:46): - Attachment: #998 CellBench > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Shians/CellBench > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:33:12): - Attachment: #999 VennDetail > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/guokai8/VennDetail > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:16:32): Unknown User (15:47:42): - Attachment: #1000 pathwayPCA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/gabrielodom/pathwayPCA > This is my first package submission to Bioconductor. I apologize in advance for my lack of experience. > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > Comments: > • Package size: we are cleaning up the .git/ directory now, in order to reduce the overall size of the package. We have one data file in inst/extdata that is 5.6Mb. > • library() calls within functions: because we use parallel computing architecture that is compatible across platforms, we use clusterEvalQ(cl, library(package)). > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (19:45:50): - Attachment: #1001 AMARETTO new package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/gevaertlab/AMARETTO > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-02-08

Unknown User (11:25:20): Unknown User (13:48:04): - Attachment: #1002 BgeeCall package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/BgeeDB/BgeeCall > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-02-09

Unknown User (02:33:39): - Attachment: #1003 scAlign > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ucdavis/quontitativebiology/tree/master/scAlign > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (02:33:40): Unknown User (18:01:51): - Attachment: #1004 scAlign > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/quon-titative-biology/scAlign > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-02-11

Unknown User (08:48:29): - Attachment: #1005 evaluomeR package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/neobernad/evaluomeR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-02-12

Unknown User (10:15:19): Unknown User (10:15:22): Unknown User (10:15:25): Unknown User (10:15:27): Unknown User (10:15:29): Unknown User (12:27:51): - Attachment: #1006 GO.db > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor/GO.db > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-02-13

Unknown User (12:25:35): Unknown User (13:24:31): - Attachment: #1007 gpuMagic package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Jiefei-Wang/gpuMagic > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:42:15): - Attachment: #1008 pwrEWAS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:42:18): Unknown User (15:07:24): - Attachment: #1009 pwrEWAS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/stefangraw/pwrEWAS > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-02-14

Unknown User (10:58:53): Unknown User (13:01:12): - Attachment: #1010 SpectralTAD > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/mdozmorov/SpectralTAD > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:01:14): Unknown User (13:16:36): - Attachment: #1011 SpectralTAD > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/dozmorovlab/spectraltad > Confirm the following by editing each check box to ‘[x]’ > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:16:40): Unknown User (13:18:20): - Attachment: #1012 SpectralTAD > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/dozmorovlab/SpectralTAD > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:53:50): Unknown User (13:53:51): Unknown User (14:25:56):

2019-02-15

Unknown User (16:32:22): - Attachment: #1013 Melissa package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository:https://github.com/andreaskapou/Melissa > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-02-16

Unknown User (19:03:56): Unknown User (20:49:16): - Attachment: #1014 scMerge > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/SydneyBioX/scMerge > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (23:51:33): Unknown User (23:54:18): Unknown User (23:54:45): Unknown User (23:56:08): Unknown User (23:56:36):

2019-02-17

Unknown User (13:49:09): - Attachment: #1015 Structstrings > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/FelixErnst/Structstrings > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-02-19

Unknown User (18:52:19): - Attachment: #1016 PoTRA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor-PoTRA/PoTRA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:52:20): Unknown User (19:28:47): - Attachment: #1017 PoTRA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor-PoTRA/PoTRA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (19:28:48): Unknown User (19:31:31): - Attachment: #1018 PoTRA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor-PoTRA/PoTRA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (19:31:32): Unknown User (19:37:15): - Attachment: #1019 PoTRA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor-PoTRA/PoTRA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-02-20

Unknown User (15:33:36): Unknown User (15:33:38): Unknown User (15:33:41): Unknown User (15:33:45): Unknown User (15:33:46): Unknown User (17:53:25): - Attachment: #1020 PoTRA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor-PoTRA/PoTRA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:53:26):

2019-02-21

Unknown User (06:39:22): Unknown User (08:29:09): - Attachment: #1021 scRecover > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/miaozhun/scRecover > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:08:59): Unknown User (13:35:28): - Attachment: #1022 Xeva : XEnograft Visualization & Analysis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bhklab/Xeva > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:03:01):

2019-02-22

Unknown User (10:25:54): - Attachment: #1023 PoTRA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:25:55): Unknown User (10:26:48): - Attachment: #1024 PoTRA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor-PoTRA/PoTRA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:26:49): Unknown User (12:47:03): - Attachment: #1025 CHETAH > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jdekanter/CHETAH > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (23:33:52): - Attachment: #1026 bodymapRat: An experiment data package that contains a SummarizedExperiment object from the Yu et al. (2014) paper that performed the rat BodyMap across 11 organs and 4 developmental stages > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/stephaniehicks/bodymapRat > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-02-25

Unknown User (10:10:45): - Attachment: #1027 fishpond > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/mikelove/fishpond > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-02-27

Unknown User (10:47:49): Unknown User (10:47:50): Unknown User (10:47:52):

2019-02-28

Unknown User (11:04:42): Unknown User (11:04:44): Unknown User (18:46:02): - Attachment: #1028 PoTRA-Package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/PoTRA-Package/Development > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:46:03): Unknown User (18:47:23): - Attachment: #1029 PoTRA-Package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/PoTRA-Package/PoTRA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-03-01

Unknown User (04:13:24): - Attachment: #1030 SubCellBarCode > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/TanerArslan/SubCellBarCode > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:22:12): - Attachment: #1031 RcwlPipelines > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hubentu/RcwlPipelines > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-03-04

Unknown User (14:43:38): - Attachment: #1032 PAST > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/IGBB/PAST > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X ] The ‘devel’ branch for new packages and features. > • [X ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-03-05

Unknown User (08:23:51): Unknown User (09:03:07): - Attachment: #1033 nanotubes > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/MalteThodberg/nanotubes > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:26:21): Unknown User (12:26:23): Unknown User (12:26:25): Unknown User (12:26:26): Unknown User (15:43:46): Unknown User (18:37:20): - Attachment: #1034 batchelor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/LTLA/batchelor > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-03-06

Unknown User (01:39:44): - Attachment: #1035 TNBC.CMS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/nachoryu/TNBC.CMS > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-03-07

Unknown User (04:46:18): - Attachment: #1036 phyloprofile > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/BIONF/PhyloProfile > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (04:46:19): Unknown User (12:17:38): - Attachment: #1037 Package submission: scds > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/kostkalab/scds > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:38:24): - Attachment: #1038 Transcriptome Annotation with Trans2Kegg > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/croesel/Trans2Kegg > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-03-08

Unknown User (03:46:39): - Attachment: #1039 PhyloProfile > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/BIONF/PhyloProfile > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:12:22): - Attachment: #1040 projectR - Reopen of Issue #433 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/genesofeve/projectR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:12:23):

2019-03-11

Unknown User (08:11:26): Unknown User (16:39:00): - Attachment: #1041 celda > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/campbio/celda > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > This is a re-submission of the package celda. The original submission is here: #910

2019-03-12

Unknown User (22:38:52): - Attachment: #1042 scGPS - Single Cell Global fate Potential of Subpopulations > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/IMB-Computational-Genomics-Lab/scGPS > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-03-13

Unknown User (11:58:02): - Attachment: #1043 TPP2D > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/nkurzaw/TPP2D > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:49:53): - Attachment: #1044 inferCNV > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/broadinstitute/inferCNV > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:49:54): Unknown User (22:00:49): - Attachment: #1045 infercnv > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/broadinstitute/infercnv > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-03-14

Unknown User (05:00:14): Unknown User (23:25:38): - Attachment: #1046 SGC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/alenxav/SGC > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-03-15

Unknown User (07:06:34): - Attachment: #1047 mbkmeans > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/drisso/mbkmeans > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (07:32:30):

2019-03-17

gamzeaydilek (07:18:38): > @gamzeaydilek has joined the channel

2019-03-19

Unknown User (05:41:14): - Attachment: #1048 Submission of RepViz > • Repository: https://github.com/ThomasFaux/RepViz > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-03-20

Unknown User (17:00:23): - Attachment: #1049 Submitting FiTnEss > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ruy204/FiTnEss > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (21:08:53): - Attachment: #1050 Submission of casc > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jamez-eh/casc > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-03-21

Unknown User (12:48:14): - Attachment: #1051 pipeFrame and enrichTF > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wzthu/pipeFrame > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:39:21): - Attachment: #1052 animalcules > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/compbiomed/animalcules > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-03-22

Unknown User (00:39:36): - Attachment: #1053 https://github.com/quon-titative-biology/scBFA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (00:39:37): Unknown User (00:41:57): - Attachment: #1054 submitting scBFA package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/quon-titative-biology/scBFA > Confirm the following by editing each check box to ‘[x]’ > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-03-23

Unknown User (15:23:55): Unknown User (15:23:56): Unknown User (15:23:58): Unknown User (15:23:59): Unknown User (15:24:00): Unknown User (15:24:02): Unknown User (15:24:03): Unknown User (15:24:04): Unknown User (15:24:05):

2019-03-24

Unknown User (22:26:30): - Attachment: #1055 dcanr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/DavisLaboratory/dcanr > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (22:57:12): - Attachment: #1056 seq2pathway > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/xyang2uchicago/seq2pathway2019 > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (22:57:13):

2019-03-25

Unknown User (07:54:38): Unknown User (13:49:53): Unknown User (23:55:14): - Attachment: #1057 ssrch: simple search engine for heterogeneous metadata > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/vjcitn/ssrch > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-03-26

Unknown User (16:32:00): - Attachment: #1058 TreeSummarizedExperiment > • Repository: https://github.com/fionarhuang/TreeSummarizedExperiment > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-03-27

Unknown User (01:02:44): - Attachment: #1059 curatedAdipoChIP: A Curated ChIP-Seq Dataset of MDI-induced Differentiated Adipocytes (3T3-L1) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/MahShaaban/curatedAdipoChIP > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (02:10:29): - Attachment: #1060 GNET2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jianlin-cheng/GNET2 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (05:11:18): - Attachment: #1061 ViSEAGO > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/abrionne/ViSEAGO > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:53:15): - Attachment: #1062 BANDITS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/SimoneTiberi/BANDITS > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:12:14): Unknown User (19:18:35): Unknown User (19:18:40):

2019-03-28

Unknown User (11:51:35): - Attachment: #1063 MBQN package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/arianeschad/mbqn > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:51:37): Unknown User (12:15:43): - Attachment: #1064 MBQN package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/arianeschad/MBQN > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-03-29

Unknown User (07:59:41): Unknown User (10:10:26): - Attachment: #1065 lipidr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ahmohamed/lipidr > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:03:00): - Attachment: #1066 sRACIPE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/vivekkohar/sRACIPE > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:35:45): - Attachment: #1067 HCABrowser > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:35:46): Unknown User (15:38:50): - Attachment: #1068 HCABrowser > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor/HCABrowser > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:48:02): - Attachment: #1069 profileplyr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/RockefellerUniversity/profileplyr > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-03-30

Unknown User (03:17:47): - Attachment: #1070 OmicsLonDA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/aametwally/OmicsLonDA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-04-01

Unknown User (11:02:42): Unknown User (11:02:44): Unknown User (11:02:46): Unknown User (11:02:48): Unknown User (11:02:50): Unknown User (11:02:51): Unknown User (11:02:52): Unknown User (11:02:55): Unknown User (11:02:56): Unknown User (11:02:58):

2019-04-02

Unknown User (12:58:08): - Attachment: #1071 Netboost > • Repository: https://github.com/PascalSchlosser/Netboost > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:58:11): Unknown User (13:03:34): - Attachment: #1072 Netboost > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/PascalSchlosser/Netboost > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:23:41): Unknown User (15:23:45): Unknown User (17:26:46): Unknown User (17:26:47): Unknown User (22:49:32): - Attachment: #1073 NBAMSeq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/reese3928/NBAMSeq > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-04-03

Unknown User (13:45:10): - Attachment: #1074 animalcules > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/compbiomed/animalcules > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:45:13): Unknown User (13:49:40): Unknown User (16:25:24): Unknown User (16:25:25):

2019-04-04

Unknown User (06:11:15): Unknown User (06:13:54): - Attachment: #1075 netboost > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/PascalSchlosser/netboost > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:10:50): - Attachment: #1076 CopyNumberPlots > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bernatgel/CopyNumberPlots > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:04:05): - Attachment: #1077 nanotatoR: structural variant annotation and classification > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/VilainLab/nanotatoR > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:04:06): Unknown User (17:14:50): Unknown User (17:37:10): Unknown User (17:37:12): Unknown User (17:37:13): Unknown User (20:28:33): - Attachment: #1078 DiscoRhythm > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/matthewcarlucci/DiscoRhythm > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-04-05

Unknown User (02:33:26): - Attachment: #1079 StructuralVariantAnnotation > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/PapenfussLab/StructuralVariantAnnotation > > Confirm the following by editing each check box to ‘[x]’ > > • [ X ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ X ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ X ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ X ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ X ] The ‘devel’ branch for new packages and features. > • [ X ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ X ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:04:40): - Attachment: #1080 CellMixS submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/almutlue/CellMixS > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:27:23): - Attachment: #1081 metagene2 > Hello, > > Our group would like to submit the metagene2 package for inclusion in BioConductor release 3.9. metagene2 is a thorough rewrite of our previous BioCondcutor package, metagene. It includes large improvements to performance as well as a new, cleaner interface and numerous additional features: > > • metagene2 now accepts discoutiguous regions, such as gene exons, allowing one to create metagenes for RNA-seq data. > • metagene2 can now accept metadata for genomic regions and input bam files, and can later use these metadata to improve its output plots > • Richer options for plotting, including grouping and facetting on arbitrary metadata columns. > • A strand specific mode for RNA-seq data > • Options for extending reads > • Plotting individual regions > > We hope you find the package to be of interest for inclusion in Bioconductor. > > Cheers, > -Eric > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ArnaudDroitLab/metagene2 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:59:40): - Attachment: #1082 SQLDataFrame > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:59:41): Unknown User (16:01:00): Unknown User (16:15:31): Unknown User (16:18:05): Unknown User (16:43:16): Unknown User (16:47:37): - Attachment: #1083 SQLDataFrame > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor/SQLDataFrame > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-04-08

Unknown User (18:15:46): Unknown User (18:15:52):

2019-04-09

Unknown User (10:41:12): Unknown User (17:21:03): - Attachment: #1084 SBGNview > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/datapplab/SBGNview > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:21:05): Unknown User (17:45:10): - Attachment: #1085 SBGNview > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/datapplab/SBGNview > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (22:54:50): - Attachment: #1086 benchmarkfdrData2019: Data and Benchmarking Results from Korthauer and Kimes et al. (2019) comparing methods to control the false discovery rate > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/stephaniehicks/benchmarkfdrData2019 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-04-10

Unknown User (04:08:41): - Attachment: #1087 SINCE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/XZouProjects/SINCE > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (07:24:00): - Attachment: #1088 puma > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/PUGEA/puma > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:36:20): - Attachment: #1089 XCIR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/SRenan/XCIR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-04-11

Unknown User (07:08:03): Unknown User (08:44:08): Unknown User (13:49:25): - Attachment: #1090 SCANVIS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/nygenome/SCANVIS > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-04-12

Unknown User (10:57:54): Unknown User (10:57:56): Unknown User (10:57:57): Unknown User (10:57:59):

2019-04-13

Unknown User (13:14:33): - Attachment: #1091 NucDyn > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/nucleosome-dynamics/NucDyn.git > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:14:35): Unknown User (13:20:10): - Attachment: #1092 NucDyn > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/nucleosome-dynamics/NucDyn > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-04-15

Unknown User (12:05:20): - Attachment: #1093 SynMut > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Koohoko/SynMut > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-04-16

Unknown User (09:51:34): Unknown User (09:52:53): Unknown User (11:41:13): - Attachment: #1094 harmony > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [X ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X ] The ‘devel’ branch for new packages and features. > • [X ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > Please note that BiocCheck() produced 2 NOTES: > > (1) “Consider shorter lines; 2 lines (0%) are > 80 characters long.” > > One of these lines is a URL and cannot be shortened. The other is in RcppExports and was automatically generated by Rcpp::compileAttributes(). > > (2) “Consider multiples of 4 spaces for line indents, 40 lines(4%) are not.” > > These lines are generated automatically by Roxygen. All source code and vignettes have 4-space indents.

Unknown User (11:41:15): Unknown User (11:46:04): - Attachment: #1095 harmony > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/immunogenomics/harmony > > Confirm the following by editing each check box to ‘[x]’ > > • [X ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X ] The ‘devel’ branch for new packages and features. > • [X ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > Please note that BiocCheck() produced 2 NOTES: > > (1) “Consider shorter lines; 2 lines (0%) are > 80 characters long.” > > One of these lines is a URL and cannot be shortened. The other is in RcppExports and was automatically generated by Rcpp::compileAttributes(). > > (2) “Consider multiples of 4 spaces for line indents, 40 lines(4%) are not.” > > These lines are generated automatically by Roxygen. All source code and vignettes have 4-space indents.

Unknown User (17:38:58):

2019-04-18

Unknown User (10:24:35): - Attachment: #1096 depap: Cancer Dependency Map data package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/uclouvain-cbio/depmap > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:40:04): - Attachment: #1097 ENCODExplorerData > We would like to submit ENCODExplorerData for inclusion in Bioconductor release 3.9. This package is a subset of our current Bioconductor package, ENCODExplorer. The Data portion of ENCODExplorer (A data.table describing every file made available by the ENCODE project) has grown too big for inclusion as a software package (Nearly 80MB). Thus, we have split the data part into this new AnnotationHub package, and kept the software part in ENCODExplorer. > > Thank you for your time, > -Eric Fournier > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ArnaudDroitLab/ENCODExplorerData > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-04-19

Unknown User (17:50:56): Unknown User (18:10:30): Unknown User (18:10:32): Unknown User (18:10:34): Unknown User (18:10:35): Unknown User (18:10:37): Unknown User (18:10:39): Unknown User (18:10:40): Unknown User (18:10:42): Unknown User (18:10:44): Unknown User (18:10:46):

2019-04-21

Unknown User (02:38:46): - Attachment: #1098 scRMD > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ChongC1990/scRMD > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-04-22

Unknown User (00:40:00): - Attachment: #1099 msdp > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/KristyWei/msdp > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:20:46): Unknown User (10:20:48):

2019-04-23

Unknown User (03:57:33): - Attachment: #1100 muscData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/HelenaLC/muscData > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:13:49): - Attachment: #1101 submission of package deltaCaptureC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/michaeldshapiro/deltaCaptureC > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:40:58): Unknown User (17:40:59): Unknown User (17:41:01): Unknown User (17:41:03): Unknown User (17:41:05): Unknown User (17:41:07): Unknown User (17:41:09): Unknown User (17:41:11):

2019-04-24

Unknown User (01:14:03): Unknown User (04:28:06): Unknown User (06:52:38): - Attachment: #1102 Mulcom Update > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • https://github.com/cisella/Mulcom.git > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (06:52:40): Unknown User (08:55:11): - Attachment: #1103 Mulcom Update > Update the following URL to point to the GitHub repository of Mulcom > the package you wish to submit to Bioconductor > > • Repository: https://github.com/cisella/Mulcom.git > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:55:13): Unknown User (12:35:39): - Attachment: #1104 Mulcom Update 2019 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/cisella/Mulcom.git > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:35:43): Unknown User (17:19:33): Unknown User (17:19:56): Unknown User (17:27:57): Unknown User (17:27:59): Unknown User (17:28:01): Unknown User (17:28:03): Unknown User (17:28:04): Unknown User (17:28:06): Unknown User (17:28:08): Unknown User (17:28:09): Unknown User (17:28:11):

2019-04-25

Unknown User (04:08:20): - Attachment: #1105 CNVassoc > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/isglobal-brge/CNVassoc > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-04-26

Unknown User (09:37:09): Unknown User (09:37:11):

2019-04-27

Unknown User (13:26:30): Unknown User (13:26:31):

2019-04-28

Unknown User (11:55:40): - Attachment: #1106 RNAmodR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/FelixErnst/RNAmodR.Data > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-04-30

Unknown User (11:51:01): Unknown User (11:51:06): Unknown User (11:51:08):

2019-05-03

Unknown User (13:51:38): - Attachment: #1107 SAMEclustering > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:51:39): Unknown User (16:42:32): - Attachment: #1108 yycunc/SAMEclustering > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:42:33): Unknown User (16:43:53): - Attachment: #1109 SAMEclustering > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:43:54): Unknown User (16:46:31): - Attachment: #1110 SAMEclustering > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yycunc/SAMEclustering > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:22:36): - Attachment: #1111 https://github.com/rezakj/iCellR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:22:37): Unknown User (17:24:32): - Attachment: #1112 iCellR bioconductor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/rezakj/iCellR > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-05-04

Unknown User (11:44:54): - Attachment: #1113 compareSingleCell > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/MarioniLab/compareSingleCell > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-05-05

Unknown User (19:03:51): Unknown User (19:04:17): Unknown User (22:05:57): - Attachment: #1114 IndexedRelations > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/LTLA/IndexedRelations > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-05-06

Unknown User (15:58:42):

2019-05-08

Unknown User (08:13:11): - Attachment: #1115 presto > • Repository: https://github.com/immunogenomics/presto > > Confirm the following by editing each check box to ‘[x]’ > > • [X ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X ] I have read the Bioconductor [Package Submission][2] > instructions. My package is consistent with the Bioconductor > [Package Guidelines][1]. > • [X ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X ] I am committed to the long-term maintenance of my package. This > includes monitoring the [support site][3] for issues that users may > have, subscribing to the [bioc-devel][4] mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ X] The ‘devel’ branch for new packages and features. > • [X ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X ] Bioconductor version control using [Git][5] > (optionally [via GitHub][6]).

2019-05-09

Unknown User (06:16:12): Unknown User (17:00:21): - Attachment: #1116 DNS contribution > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/zhezhenwang/DNS > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:00:23): Unknown User (17:01:45): - Attachment: #1117 DNS contribution > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/xyang2uchicago/DNS > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:01:47): Unknown User (17:05:21): - Attachment: #1118 DNS contribution > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/zhezhenwang/DNS/DNS > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:05:23): Unknown User (17:10:32): - Attachment: #1119 DNS contribution > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/zhezhenwang/DNS > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:10:34): Unknown User (17:13:58): - Attachment: #1120 DNS contribution > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/xyang2uchicago/DNS > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-05-14

Unknown User (10:44:41): Unknown User (10:44:43):

2019-05-15

Unknown User (10:25:49): - Attachment: #1121 KnowSeq R package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/CasedUgr/KnowSeq > > Confirm the following by editing each check box to ‘[x]’ > > • [ X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ X] The ‘devel’ branch for new packages and features. > • [X ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-05-17

Unknown User (00:51:32): - Attachment: #1122 TreeExp > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jingwyang/TreeExp > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:10:02): - Attachment: #1123 HMP2Data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jstansfield0/HMP2Data > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-05-18

Unknown User (12:11:31): - Attachment: #1124 R package gwasrapidd submission > Note > > Please note that I am aware that BiocCheck::BiocCheck() should give no errors and no warnings. I have one warning still: > > "The following files are over 5MB in size: '.git/objects/pack/pack-fb9aec1c48d78e3166698db47359a703612078be.pack'" > > I have followed the instructions here: https://bioconductor.org/developers/how-to/git/remove-large-data/ but to no avail. > > Submission form > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ramiromagno/gwasrapidd > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-05-19

Unknown User (14:27:09): Unknown User (14:27:14): Zhi Yang (15:52:29): > @Zhi Yang has joined the channel

2019-05-20

Unknown User (17:59:04): - Attachment: #1125 MaAsLiN2 package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/biobakery/maaslin2 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:59:06): Unknown User (18:00:52): - Attachment: #1126 MaAsLin2 package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/biobakery/Maaslin2 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-05-21

Unknown User (09:33:46): - Attachment: #1127 TOAST > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ziyili20/TOAST > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:24:37):

2019-05-22

Brendan Innes (15:47:22): > @Brendan Innes has joined the channel

2019-05-23

Unknown User (05:27:54): - Attachment: #1128 GENEMABR submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/TaoDFang/GENEMABR > Confirm the following by editing each check box to ‘[x]’ > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:31:40): - Attachment: #1129 HCAMatrixBrowser > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor/HCAMatrixBrowser > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (21:29:15): - Attachment: #1130 AWFisher package submission to Bioconductor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Caleb-Huo/AWFisher > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-05-27

Unknown User (07:08:03): - Attachment: #1131 NoRCE - Non-coding RNA sets Cis Enrichment Tool > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/guldenolgun/NoRCE > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-05-28

Unknown User (08:46:31): Unknown User (10:24:50): - Attachment: #1132 https://github.com/Aufiero/circRNAprofiler > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:24:52): Unknown User (10:53:55): - Attachment: #1133 circRNAprofiler > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Aufiero/circRNAprofiler > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-05-29

Unknown User (09:07:02): - Attachment: #1134 Testing SPB - expect new failure > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/lshep/makeapackage > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:08:07): - Attachment: #1135 Testing SPB - testing success > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/lshep/LorisWorld > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:48:44): Unknown User (09:48:52): Unknown User (12:00:59): - Attachment: #1136 SigsPack > • Repository: https://github.com/bihealth/SigsPack > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-05-31

Unknown User (12:48:00):

2019-06-02

Unknown User (08:25:14): - Attachment: #1137 proDA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/const-ae/proDA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-06-03

Unknown User (11:21:20): - Attachment: #1138 https://github.com/xiaowangCN/GeneDMRs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:21:30): Unknown User (11:24:55): - Attachment: #1139 GeneDMRs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/xiaowangCN/GeneDMRs > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:29:06): - Attachment: #1140 GeneDMRs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/xiaowangCN/GeneDMRs > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:29:09):

2019-06-04

Unknown User (23:53:25): - Attachment: #1141 HiLDA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/USCbiostats/HiLDA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-06-05

Unknown User (14:31:30):

2019-06-06

Unknown User (07:34:26): Unknown User (07:47:55): Unknown User (15:16:30): Unknown User (15:16:32): Unknown User (15:16:34): Unknown User (15:16:36):

2019-06-07

Unknown User (15:55:04): - Attachment: #1142 MetaVolcanoR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/csbl-usp/MetaVolcanoR > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-06-10

Unknown User (09:09:09): - Attachment: #1143 Testing SPB - expect fail > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/lshep/makeapackage > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:09:10): Unknown User (09:10:22): - Attachment: #1144 Testing SPB expect failure > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/lshep/Lorisworld > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:10:24): Unknown User (09:11:33): - Attachment: #1145 Testing SPB - expect success > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/lshep/LorisWorld > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:11:55):

2019-06-12

Unknown User (07:39:20): - Attachment: #1146 New package fcScan: features cluster Scan > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/pkhoueiry/fcScan.git > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (07:39:22): Unknown User (07:44:18): - Attachment: #1147 Submit new package “fcScan: features cluster Scan” > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/pkhoueiry/fcScan > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-06-13

Unknown User (14:33:07): - Attachment: #1148 gemini > GEMINI: A variational Bayesian approach to identify genetic interactions from combinatorial CRISPR screens > > This package is being submitted to Bioconductor upon conditional acceptance of a corresponding manuscript. The contents of the package are described in detail within the manuscript, as well as with the accompanying documentation. > > • Repository: https://github.com/sellerslab/gemini > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:14:16): Unknown User (16:14:18): Unknown User (16:14:20):

2019-06-14

Unknown User (14:52:49): - Attachment: #1149 netDx > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/BaderLab/netDx.examples > > Confirm the following by editing each check box to ‘[x]’ > > • [X ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-06-17

Unknown User (13:30:28): - Attachment: #1150 MouseGastrulationData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/MarioniLab/MouseGastrulationData > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-06-18

Unknown User (19:15:51): - Attachment: #1151 ascend > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/powellgenomicslab/ascend > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-06-19

Unknown User (07:35:55): Unknown User (11:17:27): - Attachment: #1152 SharedObject > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Jiefei-Wang/sharedObject > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:17:30): Unknown User (11:21:04): - Attachment: #1153 SharedObject > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Jiefei-Wang/SharedObject > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Brendan Innes (15:11:49): > @Brendan Innes has left the channel

Unknown User (16:31:07): - Attachment: #1154 ncGTW > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ChiungTingWu/ncGTW > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-06-20

Unknown User (08:12:47): - Attachment: #1155 RNAmodR.ML > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/FelixErnst/RNAmodR.ML > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:45:24): Unknown User (10:45:26): Unknown User (10:45:28):

2019-06-21

Unknown User (05:50:59): - Attachment: #1156 TENxBUSData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/BUStools/TENxBUSData > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-06-22

Unknown User (05:35:07): - Attachment: #1157 tradeSeq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/statOmics/tradeSeq > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:02:48):

2019-06-24

Unknown User (00:23:42): - Attachment: #1158 binomialRF > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/SamirRachidZaim/binomialRF > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-06-25

Unknown User (00:52:07): - Attachment: #1159 CrossICC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bioinformatist/CrossICC > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (03:01:48): Unknown User (06:37:54): - Attachment: #1160 ENTC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (06:37:56): Unknown User (09:08:19): - Attachment: #1161 ENTC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/zhangli1109/ENTC > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:34:23): Unknown User (09:35:23): - Attachment: #1162 ENTC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/zhangli1109/ENTC > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:35:25): Unknown User (09:38:08): Unknown User (09:54:48): - Attachment: #1163 MOSim > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Neurergus/mosim > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:54:49): Unknown User (10:01:30): - Attachment: #1164 MOSim > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Neurergus/MOSim > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-06-27

Unknown User (03:25:32): - Attachment: #1165 gramm4R > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/chentianlu/gramm4R > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (03:25:33): Unknown User (03:28:50): - Attachment: #1166 gramm4R > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/chentianlu/GRaMM_R > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (03:28:51): Unknown User (03:51:36): - Attachment: #1167 gramm4R > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/chentianlu/gramm4R > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:37:25): - Attachment: #1168 InterMineR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/intermine/InterMineR > > Confirm the following by editing each check box to ‘[x]’ > > • [ X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ X] The ‘devel’ branch for new packages and features. > • [ X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:37:27): Lauren Fitch (15:43:42): > @Lauren Fitch has joined the channel

2019-07-01

Unknown User (08:48:36): - Attachment: #1169 ReactomeGSA > • Repository: https://github.com/reactome/ReactomeGSA > > Accompanying data package: > > • Repository: https://github.com/reactome/ReactomeGSA.data > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor [Package Submission][2] > instructions. My package is consistent with the Bioconductor > [Package Guidelines][1]. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the [support site][3] for issues that users may > have, subscribing to the [bioc-devel][4] mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using [Git][5] > (optionally [via GitHub][6]).

Unknown User (08:48:38): Unknown User (08:50:43): - Attachment: #1170 ReactomeGSA > • Repository: https://github.com/reactome/ReactomeGSA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor [Package Submission][2] > instructions. My package is consistent with the Bioconductor > [Package Guidelines][1]. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the [support site][3] for issues that users may > have, subscribing to the [bioc-devel][4] mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using [Git][5] > (optionally [via GitHub][6]).

Unknown User (08:51:10): - Attachment: #1171 ReactomeGSA.data > • Repository: https://github.com/reactome/ReactomeGSA.data > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor [Package Submission][2] > instructions. My package is consistent with the Bioconductor > [Package Guidelines][1]. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the [support site][3] for issues that users may > have, subscribing to the [bioc-devel][4] mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using [Git][5] > (optionally [via GitHub][6]).

Unknown User (11:48:01): - Attachment: #1172 NiftiArray Package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/muschellij2/niftiArray > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > Covers imaging - which can be related to genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:48:05): Unknown User (11:49:34): - Attachment: #1173 NiftiArray Package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/muschellij2/NiftiArray > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > Covers imaging - which can be related to genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:31:05): Lauren Fitch (13:41:26): > @Lauren Fitch has left the channel

Unknown User (16:47:42): Unknown User (17:47:49):

2019-07-02

Unknown User (07:21:34): - Attachment: #1174 DMCFB > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/shokoohi/DMCFB > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (22:30:35): Unknown User (22:30:56): Unknown User (23:20:27): - Attachment: #1175 idr2d > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/kkrismer/idr2d > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-07-03

Unknown User (12:50:54): - Attachment: #1176 sojourner > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/sheng-liu/sojourner.git > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput single molecule tracking data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:50:55): Unknown User (13:51:19): - Attachment: #1177 sojourner > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/sheng-liu/sojourner > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput single molecule tracking data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-07-04

Unknown User (15:28:46):

2019-07-05

Unknown User (12:55:20): - Attachment: #1178 cellassign > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/kieranrcampbell/cellassign > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-07-09

Unknown User (10:52:41): Unknown User (10:52:42): Unknown User (10:52:44):

2019-07-10

Unknown User (23:45:58): - Attachment: #1179 prioGene > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/huerqiang/prioGene > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-07-14

Unknown User (21:36:42): - Attachment: #1180 Submission of “APAlyzer” package to Bioconductor > Dear Bioconductor developers, > > I would like to submit my “APAlyzer” R package to Bioconductor. The current package has been checked using ‘R CMD build’, ‘R CMD check’ and ‘R CMD BiocCheck’. And please notice that the package supports both Linux and Mac, but doesn’t support window. > > • Repository: https://github.com/RJWANGbioinfo/APAlyzer > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-07-16

Unknown User (09:14:47): - Attachment: #1181 SEtools > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/plger/SEtools > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:13:47): - Attachment: #1182 oppti > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Huang-lab/oppti > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-07-18

Unknown User (09:00:53): - Attachment: #1183 AlphaBeta > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jlab-code/AlphaBeta > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:47:51): Unknown User (10:47:52): Unknown User (10:47:54):

2019-07-19

Unknown User (11:56:05): Unknown User (11:56:45):

2019-07-22

Unknown User (10:52:30): - Attachment: #1184 brendaDb > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/y1zhou/brendaDb > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-07-23

Unknown User (14:09:40): - Attachment: #1185 TCseq > Dear developer, > > thank you for the package. I have tca in correct but when I run countReads and it showed me could not find the bam files. Any ideas? Thank you very much. > tca > An object of class “TCA” > @design > sampleid timepoint group bamfile > 1 1 E16 1 E16WTc_chr.bam > 2 2 P0 2 P0H2_chr.bam > > @genomicFeature > chr start end id > 1 chr1 3116838 3117177 peak1 > 2 chr1 3117299 3117603 peak2 > 3 chr1 3361023 3361221 peak3 > 4 chr1 3372724 3372891 peak4 > 5 chr1 3395611 3395733 peak5 > 132621 more rows … > > @clusterRes > An object of class “clust” > > tca <- countReads(tca, dir=‘C:/Users/rsong/Downloads/chromVAR/TCseq’) > Error in countReads(tca, dir = “C:/Users/rsong/Downloads/chromVAR/TCseq”) : > Can not find ‘BAMfile’ in design, please check if the correspoinding field is missing or uses a different column name.

Unknown User (14:09:42): Unknown User (14:29:51): - Attachment: #1186 TCseq > Dear developer, > > thank you for the package. I have tca in correct but when I run countReads and it showed me could not find the bam files. Any ideas? Thank you very much. > tca > An object of class “TCA” > @design > sampleid timepoint group bamfile > 1 1 E16 1 E16WTc_chr.bam > 2 2 P0 2 P0H2_chr.bam > > @genomicFeature > chr start end id > 1 chr1 3116838 3117177 peak1 > 2 chr1 3117299 3117603 peak2 > 3 chr1 3361023 3361221 peak3 > 4 chr1 3372724 3372891 peak4 > 5 chr1 3395611 3395733 peak5 > 132621 more rows … > > @clusterRes > An object of class “clust” > > tca <- countReads(tca, dir=‘C:/Users/rsong/Downloads/chromVAR/TCseq’) > Error in countReads(tca, dir = “C:/Users/rsong/Downloads/chromVAR/TCseq”) : > Can not find ‘BAMfile’ in design, please check if the correspoinding field is missing or uses a different column name. > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:29:52):

2019-07-24

Unknown User (10:30:21): - Attachment: #1187 IgGeneUsage > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/snaketron/IgGeneUsage > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:00:28): - Attachment: #1188 calm > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/k22liang/calm > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-07-25

Unknown User (12:14:08): - Attachment: #1189 Autotuner > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/crmclean/Autotuner > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:35:06): - Attachment: #1190 Sscore2 submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/harrisgm/Sscore2 > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:42:28): - Attachment: #1191 brainflowprobes package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/LieberInstitute/brainflowprobes > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:44:20): - Attachment: #1192 GmicR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Rvirgenslane/GmicR > > Confirm the following by editing each check box to ‘[x]’ > > • [X ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ X] The ‘devel’ branch for new packages and features. > • [ X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-07-26

Unknown User (05:33:32): - Attachment: #1193 ssPATHS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ratschlab/projects2019-ssPATHS > > Confirm the following by editing each check box to ‘[x]’ > > • [ x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x ] The ‘devel’ branch for new packages and features. > • [ x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (05:33:34): Unknown User (05:37:33): - Attachment: #1194 ssPATHS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ratschlab/ssPATHS > > Confirm the following by editing each check box to ‘[x]’ > > • [ x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x ] The ‘devel’ branch for new packages and features. > • [ x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-08-02

Unknown User (13:16:38): Unknown User (18:06:36): - Attachment: #1195 RiboR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ribosomeprofiling/RiboR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:06:37): Unknown User (18:07:58): - Attachment: #1196 RiboR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ribosomeprofiling/RiboR/tree/master/ribor > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:07:59): Unknown User (18:12:59): - Attachment: #1197 RiboR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ribosomeprofiling/RiboR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:13:00): Unknown User (18:14:02): - Attachment: #1198 ribor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ribosomeprofiling/RiboR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:14:04): Unknown User (18:15:23): - Attachment: #1199 ribor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ribosomeprofiling/RiboR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:15:25): Unknown User (18:15:50): - Attachment: #1200 ribor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ribosomeprofiling/ribor > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-08-05

Unknown User (07:00:26): Unknown User (16:02:53):

2019-08-06

Unknown User (12:50:26): - Attachment: #1201 muscat > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/HelenaLC/muscat > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:22:17):

2019-08-07

Unknown User (09:17:18): Unknown User (09:18:12): Unknown User (14:23:24): Unknown User (17:19:10): Unknown User (17:19:12):

2019-08-08

Unknown User (06:18:00): - Attachment: #1202 Spaniel > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/RachelQueen1/Spaniel > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-08-12

Unknown User (05:52:59): - Attachment: #1203 Qtlizer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/matmu/Qtlizer > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-08-13

Unknown User (17:28:15):

2019-08-14

Unknown User (01:18:46): - Attachment: #1204 methcp > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/boyinggong/methcp > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (03:41:20): - Attachment: #1205 pulsedSilac > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/marcpaga/pulsedSilac > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:54:51): Unknown User (11:54:52): Unknown User (11:54:54): Unknown User (11:54:55): Unknown User (11:54:57): Unknown User (16:18:20): Unknown User (18:49:27): - Attachment: #1206 SingleR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/LTLA/SingleR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (22:45:25): - Attachment: #1207 FlowSorted.Blood.WGBS.BLUEPRINT > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/stephaniehicks/FlowSorted.Blood.WGBS.BLUEPRINT > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-08-15

Unknown User (09:27:27):

2019-08-16

Unknown User (15:08:10): - Attachment: #1208 New package: blacksheepr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ruggleslab/blackSheepR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-08-17

Unknown User (18:29:56): - Attachment: #1209 GenomicOZone > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/zh9118/GenomicOZone > > Confirm the following by editing each check box to ‘[x]’ > > • [ x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x ] The ‘devel’ branch for new packages and features. > • [ x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:29:57): Unknown User (18:45:05): - Attachment: #1210 GenomicOZone > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x ] The ‘devel’ branch for new packages and features. > • [ x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:45:07): Unknown User (18:52:01): - Attachment: #1211 GenomicOZone > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/zh9118/GenomicOZone > > Confirm the following by editing each check box to ‘[x]’ > > • [ x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x ] The ‘devel’ branch for new packages and features. > • [ x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (19:10:11): - Attachment: #1212 GenomicOZone > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/zh9118/GenomicOZone > > Confirm the following by editing each check box to ‘[x]’ > > • [ x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x ] The ‘devel’ branch for new packages and features. > • [ x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (19:10:13): Unknown User (19:11:24): Unknown User (19:12:26): - Attachment: #1213 GenomicOZone > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/zh9118/GenomicOZone > > Confirm the following by editing each check box to ‘[x]’ > > • [ x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x ] The ‘devel’ branch for new packages and features. > • [ x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (19:12:27): Unknown User (19:12:59): Unknown User (19:21:35): Unknown User (19:26:50): - Attachment: #1214 GenomicOZone > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/zh9118/GenomicOZone > > Confirm the following by editing each check box to ‘[x]’ > > • [ x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x ] The ‘devel’ branch for new packages and features. > • [ x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (19:26:52): Unknown User (19:38:42):

2019-08-19

Unknown User (16:30:53): Unknown User (16:30:55): Unknown User (16:30:56):

2019-08-21

Unknown User (11:37:50): Unknown User (11:37:52): Unknown User (11:37:53): Unknown User (18:40:43): - Attachment: #1215 ALPS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/itsvenu/ALPS > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-08-25

Unknown User (17:56:28):

2019-08-26

Unknown User (14:09:07): - Attachment: #1216 microbiomeDASim > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/williazo/microbiomeDASim > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:14:14): - Attachment: #1217 signatureSearchData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yduan004/signatureSearchData > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:31:39): Unknown User (16:45:44):

2019-08-27

Unknown User (06:32:49): - Attachment: #1218 Package submission request for waddR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/goncalves-lab/waddR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (06:46:14): Unknown User (08:33:10): Unknown User (13:22:30): Unknown User (13:22:32): Unknown User (13:22:34): Unknown User (18:04:25): - Attachment: #1219 BioTIP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:04:27): Unknown User (18:06:45): - Attachment: #1220 BioTIP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/xyang2uchicago/BioTIP > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:07:32):

2019-08-28

Unknown User (05:26:15): - Attachment: #1221 MEB > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/FocusPaka/MEB > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:46:03):

2019-08-30

Unknown User (12:44:25): - Attachment: #1222 AltWrapper > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Jiefei-Wang/AltWrapper > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:25:29): Unknown User (14:25:30):

2019-09-02

Unknown User (16:02:31): - Attachment: #1223 peakPantheR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/phenomecentre/peakPantheR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-09-03

Unknown User (08:02:44): - Attachment: #1224 lionessR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/dn070017/lionessR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:24:39): - Attachment: #1225 DMCFB Package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/shokoohi/DMCFB > > Confirm the following by editing each check box to ‘[x]’ > > • [ x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:24:41): Unknown User (13:49:52): - Attachment: #1226 RNAsense > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/marcusrosenblatt/RNAsense > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:49:53): Unknown User (13:53:59): - Attachment: #1227 RNAsense > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/marcusrosenblatt/RNAsense > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:54:52):

2019-09-04

Unknown User (12:34:02): - Attachment: #1228 gscreend package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/imkeller/gscreend > > Confirm the following by editing each check box to ‘[x]’ > > • [X ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X ] The ‘devel’ branch for new packages and features. > • [X ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-09-05

Unknown User (09:09:52): Unknown User (12:37:40): - Attachment: #1229 BiocSet > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Kayla-Morrell/BiocSet > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:48:32): Unknown User (14:48:34): Unknown User (14:48:36):

2019-09-06

Unknown User (12:59:49): - Attachment: #1230 bioverbs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/acidgenomics/bioverbs > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > The bioverbs package is a dependency of my basejump toolkit.

Unknown User (13:05:40): - Attachment: #1231 goalie > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/acidgenomics/goalie > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > The goalie package is a dependency of my basejump toolkit. > > An updated vignette is in progress and will be added to the master branch.

Unknown User (13:09:36): - Attachment: #1232 acidroxygen > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/acidgenomics/acidroxygen > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > The acidroxygen package defines shared roxygen documentation parameters used across my Acid Genomics R packages.

Unknown User (13:11:29): - Attachment: #1233 acidtest > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/acidgenomics/acidtest > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > The acidtest package defines example objects used for unit testing via testthat across the Acid Genomics R packages.

Unknown User (13:14:14): - Attachment: #1234 syntactic > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/acidgenomics/syntactic > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > The syntactic package is a dependency of my basejump toolkit.

Unknown User (13:15:50): - Attachment: #1235 transformer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/acidgenomics/transformer > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > The transformer package is a dependency of my basejump toolkit.

Unknown User (13:17:31): - Attachment: #1236 freerange > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/acidgenomics/freerange > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > The freerange package is a dependency of my basejump toolkit.

Unknown User (13:20:07): - Attachment: #1237 brio > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/acidgenomics/brio > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > The brio package is a dependency of my basejump toolkit.

Unknown User (13:23:34): - Attachment: #1238 basejump > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/acidgenomics/basejump > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > The basejump package is a toolkit for bioinformatics. It provides method support for genome annotations, metadata, quality control, and works primarily with SummarizedExperiment and GenomicRanges.

Unknown User (14:45:41): - Attachment: #1239 WGSmapp > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/rujinwang/WGSmapp > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-09-09

Unknown User (11:20:00): Unknown User (11:22:07): - Attachment: #1240 SCOPE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/rujinwang/SCOPE/tree/master/package > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:22:12): Unknown User (11:53:35): - Attachment: #1241 fcoex > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/csbl-usp/fcoex > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:43:53): - Attachment: #1242 SCOPE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/rujinwang/SCOPE > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (19:03:04): - Attachment: #1243 Submission package: PERFect > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/katiasmirn/PERFect > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-09-10

Unknown User (14:55:01): Unknown User (14:57:11): Unknown User (17:04:50): - Attachment: #1244 cliqueMS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/osenan/cliqueMS > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:51:12): - Attachment: #1245 TADCompare > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/dozmorovlab/TADCompare > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-09-11

Unknown User (11:55:40): Unknown User (13:26:02):

2019-09-12

Unknown User (03:05:23): - Attachment: #1246 Upgrade of DMRcatedata and DMRcate > Hi Nitesh and Lori, > Further to the bioc-devel issue on 22/8, at Nitesh’s suggestions I have made DMRcatedata into an ExperimentHub package - see link below. This is to accompany the new version of DMRcate, whose git has also been updated. > • Repositories: > • https://github.com/timpeters82/DMRcatedata > • https://github.com/timpeters82/DMRcate-devel > > DMRcate_2.0.0 should pass R CMD check and R CMD BiocCheck, but I am unsure about DMRcatedata_2.0.0 because it needs to be incorporated into ExperimentHub first. > > Many thanks, > Tim > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (03:05:24): Unknown User (03:08:07): - Attachment: #1247 Update of DMRcatedata and DMRcate > Hi Nitesh and Lori, > Further to the bioc-devel issue on 22/8, at Nitesh’s suggestions I have made DMRcatedata into an ExperimentHub package - see link below. This is to accompany the new version of DMRcate, whose git has also been updated. > > Repository: > https://github.com/timpeters82/DMRcatedata > > DMRcate_2.0.0 should pass R CMD check and R CMD BiocCheck, but I am unsure about DMRcatedata_2.0.0 because it needs to be incorporated into ExperimentHub first. > > Many thanks, > Tim > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor [Package Submission][2] > instructions. My package is consistent with the Bioconductor > [Package Guidelines][1]. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the [support site][3] for issues that users may > have, subscribing to the [bioc-devel][4] mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using [Git][5] > (optionally [via GitHub][6]).

Unknown User (08:25:53):

2019-09-13

Unknown User (02:41:27): - Attachment: #1248 peco > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jhsiao999/peco > > Confirm the following by editing each check box to ‘[x]’ > > • [ X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:16:32): - Attachment: #1249 scPCA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/PhilBoileau/scPCA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-09-14

Unknown User (12:27:32): - Attachment: #1250 flowSpy > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/JhuangLab/flowSpy > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > R package link: flowSpy_1.2.7.tar.gz

Unknown User (12:27:33): Unknown User (12:29:48): - Attachment: #1251 flowSpy > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/JhuangLab/flowSpy > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-09-15

Unknown User (20:37:49): - Attachment: #1252 selectKSigs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/USCbiostats/selectKSigs > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-09-16

Unknown User (01:33:32): - Attachment: #1253 schex > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/SaskiaFreytag/schex > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (07:32:08): - Attachment: #1254 scDblFinder > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/plger/scDblFinder > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (23:12:36): - Attachment: #1255 scTGIF > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/rikenbit/scTGIF > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-09-17

Unknown User (22:14:39): - Attachment: #1256 bcbioRNASeq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > Note that this package depends on basejump (#1238), acidplots, DESeqAnalysis, and bcbioBase, which are currently only available via GitHub.

Unknown User (22:14:41): Unknown User (22:16:06): - Attachment: #1257 bcbioRNASeq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hbc/bcbioRNASeq > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > Note that this package depends on basejump (#1238), acidplots, DESeqAnalysis, and bcbioBase, which are currently only available via GitHub.

Unknown User (22:18:25): - Attachment: #1258 bcbioSingleCell > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hbc/bcbioSingleCell > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > Note that this package depends on basejump (#1238), acidplots, and bcbioBase, which are currently only available via GitHub. See also related package bcbioRNASeq (#1257).

2019-09-18

Unknown User (05:41:09): - Attachment: #1259 flowSpecs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jtheorell/flowSpecs > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (06:43:22): - Attachment: #1260 optimalFlow > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/HristoInouzhe/optimalFlowData > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:31:29): Unknown User (10:32:37): Unknown User (10:35:06): Unknown User (10:35:15): Unknown User (11:06:01):

2019-09-19

Unknown User (09:44:02): Unknown User (14:52:47):

2019-09-20

Unknown User (10:58:30):

2019-09-23

Unknown User (06:00:22): - Attachment: #1261 DEWSeq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/EMBL-Hentze-group/DEWSeq > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-09-24

Unknown User (04:06:58): - Attachment: #1262 LinkHD-Bioconductor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/lauzingaretti/LinkHD > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (04:49:43): - Attachment: #1263 OmnipathR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/saezlab/OmnipathR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:32:25): Unknown User (15:32:26): Unknown User (15:32:27): Unknown User (16:54:24): - Attachment: #1264 iCellR_1.1.2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/rezakj/iCellR > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:54:26):

2019-09-26

Unknown User (08:12:27): - Attachment: #1265 struct > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/computational-metabolomics/struct > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:13:40): - Attachment: #1266 structToolbox > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/computational-metabolomics/structToolbox > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:15:40): - Attachment: #1267 target > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/MahShaaban/target > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:16:32): - Attachment: #1268 pmp > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/computational-metabolomics/pmp > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:19:05): - Attachment: #1269 sbcms > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/computational-metabolomics/sbcms > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:53:24): - Attachment: #1270 biscuiteerData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/trichelab/biscuiteerData > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-09-27

Unknown User (10:09:20): Unknown User (10:09:22): Unknown User (10:09:24): Unknown User (15:42:43): Unknown User (15:42:44):

2019-10-01

Unknown User (00:14:01): - Attachment: #1271 ASpediaFI > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/nachoryu/ASpediaFI > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:37:47): - Attachment: #1272 netboxr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/mil2041/netboxr > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:56:35): Unknown User (17:08:07): Unknown User (17:08:08): Unknown User (17:08:13): Unknown User (17:08:15):

2019-10-03

Unknown User (02:27:26): Unknown User (02:27:30): Unknown User (02:55:35): - Attachment: #1273 CNVfilteR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jpuntomarcos/CNVfilteR > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:56:00): - Attachment: #1274 GCSscore > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/harrisgm/GCSscore > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:51:50): - Attachment: #1275 SAIGEgds > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/zhengxwen/SAIGEgds > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-10-04

Unknown User (04:06:49): - Attachment: #1276 methrix > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/CompEpigen/methrix > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:23:34): - Attachment: #1277 MSstatsSampleSize > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Vitek-Lab/MSstatsSampleSize > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (21:52:35): - Attachment: #1278 methylCC: estimating the cell composition in whole blood samples using DNA methylation data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/stephaniehicks/methylCC > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-10-06

Unknown User (20:18:20): - Attachment: #1279 mitch > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (20:18:22): Unknown User (20:24:51): - Attachment: #1280 mitch > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/markziemann/mitch > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-10-07

Unknown User (07:15:37): - Attachment: #1281 JASPAR2020 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/da-bar/JASPAR2020 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-10-08

Unknown User (09:31:33): - Attachment: #1282 MACSQuantifyR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Peyronlab/MACSQuantifyR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-10-09

Unknown User (07:57:55): Unknown User (13:04:41): - Attachment: #1283 HCAExplorer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor/HCAExplorer > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-10-10

Unknown User (14:33:54): Unknown User (14:33:55): Unknown User (14:33:57): Unknown User (14:33:58): Unknown User (14:33:59): Unknown User (14:34:01): Unknown User (14:34:03): Unknown User (16:27:19): - Attachment: #1284 biobtreeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/tamerh/biobtreeR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-10-11

Unknown User (04:44:31): - Attachment: #1285 RTIGER: A Robust HMM-based Model for genotyping-by-sequencing and Recombination Breakpoints Identification. > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/rfael0cm/RTIGER > > Confirm the following by editing each check box to ‘[x]’ > > • [X ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X ] The ‘devel’ branch for new packages and features. > • [X ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (04:51:24): - Attachment: #1286 tartare - biocViews: ExperimentData, MassSpectrometryData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/cpanse/tartare/ > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput mass spec data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (05:24:00): - Attachment: #1287 ceRNAnetsim > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/selcenari/ceRNAnetsim > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:48:40):

2019-10-14

Unknown User (20:15:50): - Attachment: #1288 iCAT > • Repository: https://github.com/BioHPC/iCAT > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-10-15

Unknown User (16:54:11): - Attachment: #1289 Submitting MMUPHin to Bioconductor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/biobakery/mmuphin > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:54:13): Unknown User (16:56:34): - Attachment: #1290 Submitting MMUPHin to Bioconductor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/biobakery/MMUPHin > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:44:15): Unknown User (17:44:17): Unknown User (17:44:18): Unknown User (17:44:21): Unknown User (17:44:23): Unknown User (17:44:25): Unknown User (17:44:26): Unknown User (17:44:28): Unknown User (17:44:29):

2019-10-16

Unknown User (06:45:09): Unknown User (13:26:51): Unknown User (13:26:52): Unknown User (13:26:54): Unknown User (15:21:44):

2019-10-17

Unknown User (11:50:45): Unknown User (11:50:46): Unknown User (11:50:48):

2019-10-18

Unknown User (15:46:26): - Attachment: #1291 MethCP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/boyinggong/MethCP > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:24:50):

2019-10-21

Unknown User (13:15:52): Unknown User (13:15:54): Unknown User (16:38:36): Unknown User (16:38:37):

2019-10-22

Unknown User (11:01:26): - Attachment: #1292 org.Mxanthus.eg.db > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/eduardoillueca/org.Mxanthus.eg.db > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:24:26): Unknown User (17:24:28): Unknown User (17:24:29): Unknown User (17:24:31):

2019-10-23

Unknown User (11:37:09): - Attachment: #1293 scMAGeCK > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/weililab/scMAGeCK > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:37:11): Unknown User (12:16:49): - Attachment: #1294 AltStat > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Jiefei-Wang/altStat > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:16:51): Unknown User (12:18:36): - Attachment: #1295 AltStat > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Jiefei-Wang/AltStat > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:24:30): - Attachment: #1296 scMAGeCK > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/weililab/scMAGeCK > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:40:36): Unknown User (14:40:55): Unknown User (14:41:28): - Attachment: #1297 AltStats > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Jiefei-Wang/AltStats > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-10-24

Unknown User (11:35:28): Unknown User (11:35:30): Unknown User (11:35:32): Unknown User (11:35:34): Unknown User (11:35:35): Unknown User (11:35:37): Unknown User (11:35:38): Unknown User (11:35:40): Unknown User (11:35:42): Unknown User (11:35:44):

2019-10-26

Unknown User (11:58:00): Unknown User (11:58:01):

2019-10-28

Unknown User (08:23:29): - Attachment: #1298 packFinder > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jackgisby/packFinder > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:29:54): Unknown User (15:29:55):

2019-10-31

Unknown User (07:14:45): - Attachment: #1299 easyreporting > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/drighelli/easyreporting > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-11-02

Unknown User (16:00:27):

2019-11-07

Unknown User (16:55:38): - Attachment: #1300 readat > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/graumannlab/readat > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:55:40):

2019-11-12

Unknown User (18:02:18): - Attachment: #1301 dittoSeq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/dtm2451/DittoSeq > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:02:20): Unknown User (18:04:25): - Attachment: #1302 dittoSeq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/dtm2451/dittoSeq > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-11-13

Unknown User (17:44:51): - Attachment: #1303 ChIP-seq signal quantifier pipeline (CSSQ) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ashwathkumar/CSSQ > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-11-17

Unknown User (22:57:45): - Attachment: #1304 snapcount package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/langmead-lab/snapcount > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-11-18

Unknown User (13:23:57):

2019-11-19

Unknown User (07:14:51): - Attachment: #1305 NPARC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Huber-group-EMBL/NPARC > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-11-20

Unknown User (09:40:46): - Attachment: #1306 granulator > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/BioVinci/granulator > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:44:30):

2019-11-21

Unknown User (10:50:29): Unknown User (16:11:05):

2019-11-25

Unknown User (13:42:33): - Attachment: #1307 dearseq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/borishejblum/dearseq > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:43:04): - Attachment: #1308 clustifyr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/rnabioco/clustifyr > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-11-27

Unknown User (00:57:13): - Attachment: #1309 Submission of new package exomePeak2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/zhenwei10/exomPeak2 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (00:57:14): Unknown User (01:03:50): - Attachment: #1310 Submission of package exomePeak2 to bioconductor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ZhenWei10/exomePeak2 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:46:15): Unknown User (17:33:29): Unknown User (17:33:31): Unknown User (17:33:32):

2019-12-02

Unknown User (23:43:11): - Attachment: #1311 curatedAdipoArray: A Curated Microarrays Dataset of MDI-induced Differentiated Adipocytes (3T3-L1) Under Genetic and Pharmacological Perturbations > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/MahShaaban/curatedAdipoArray > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-12-04

Unknown User (13:10:43): - Attachment: #1312 PubScore > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/csbl-usp/PubScore > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:31:10): - Attachment: #1313 ROSeq - A Rank Based Approach to Modeling Gene Expression > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/krishan57gupta/ROSeq > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-12-06

Unknown User (03:57:45): - Attachment: #1314 granulator > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Novartis/granulator.git > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (03:57:47): Unknown User (04:03:31): - Attachment: #1315 granulator > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Novartis/granulator.git > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (04:03:32): Unknown User (10:40:51):

2019-12-08

Unknown User (08:44:29): - Attachment: #1316 iCTC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/krishan57gupta/iCTC > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:44:31):

2019-12-09

Unknown User (07:00:22): - Attachment: #1317 granulator > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Novartis/granulator > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-12-10

Unknown User (13:36:53): - Attachment: #1318 basilisk > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/LTLA/basilisk > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:52:09): - Attachment: #1319 FRASER > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/gagneurlab/FRASER > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:52:11):

2019-12-12

Unknown User (05:54:36): - Attachment: #1320 FRASER > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/gagneurlab/FRASER > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:09:09): - Attachment: #1321 SimFFPE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/LanyingWei/SimFFPE > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-12-16

Unknown User (11:33:05): - Attachment: #1322 rSWeeP: Representations large biological sequences datasets in compact vectors on an R platform. > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com//DanrleyRF/rSWeeP > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ ]x The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:33:07): Unknown User (11:57:39): - Attachment: #1323 rSWeeP: Representations large biological sequences datasets in compact vectors on an R platform. > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/DanrleyRF/rSWeeP > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:59:22): - Attachment: #1324 TreeAndLeaf > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/sysbiolab/TreeAndLeaf > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-12-17

Unknown User (10:07:02): - Attachment: #1325 Predicting disease progression based on methylation correlated blocks using multiple models > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/whirlsyu/EnMCB > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:07:05): Unknown User (10:12:03): - Attachment: #1326 EnMCB: Predicting disease progression based on methylation correlated blocks using multiple models > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/whirlsyu/EnMCB/tree/master/enMCB > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:12:05): Unknown User (10:46:34): - Attachment: #1327 EnMCB > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/whirlsyu/EnMCB > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-12-18

Shubham Gupta (17:19:43): > @Shubham Gupta has joined the channel

Unknown User (17:50:43): - Attachment: #1328 New package for the alignment of mass-spectrometer runs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/shubham1637/DIAlignR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2019-12-19

Unknown User (15:22:51): - Attachment: #1329 pcitRif > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/cbiagii/pcitRif > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:24:11): Unknown User (15:24:14):

2019-12-23

Unknown User (11:39:52): Unknown User (11:39:56):

2019-12-30

Unknown User (10:25:09): Unknown User (10:25:12):

2020-01-06

Unknown User (01:41:42): - Attachment: #1330 ttBulk: Friendly tidy wrappers for streamlined bulk transcriptional analysis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/stemangiola/ttBulk > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (05:08:54): - Attachment: #1331 SingleCellSignalR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/SCA-IRCM/SingleCellSignalR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (05:08:56): Unknown User (05:10:46): - Attachment: #1332 SingleCellSignalR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/SCA-IRCM/SingleCellSignalR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:21:08): Unknown User (11:21:12): Unknown User (11:21:15): Unknown User (11:21:19):

2020-01-07

Unknown User (12:46:41): - Attachment: #1333 tscR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/fpsanz/tscR > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-01-08

Unknown User (19:16:35): - Attachment: #1334 ctgGEM > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bicbioeng/ctgGEM > Confirm the following by editing each check box to ‘[x]’ > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-01-13

Unknown User (20:32:48): - Attachment: #1335 cmapR submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/cmap/cmapR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (21:43:05): - Attachment: #1336 MEAT > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/sarah-voisin/MEAT > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-01-14

Unknown User (10:13:53): Unknown User (10:14:04): Unknown User (10:14:11): Unknown User (10:14:19): Unknown User (11:12:06): - Attachment: #1337 smiRk > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Krutik6/smiRk > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-01-15

Unknown User (05:11:46): Unknown User (05:11:48): Unknown User (05:11:49): Unknown User (05:11:51): Unknown User (05:11:53): Unknown User (11:21:31): - Attachment: #1338 ROCpAI > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/juanpegarcia/ROCpAI > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:21:33): Unknown User (11:27:19): - Attachment: #1339 ROCpAI > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/juanpegarcia/ROCpAI > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:27:21): Unknown User (12:02:14): - Attachment: #1340 frenchFISH > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/markowetzlab/frenchFISH > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:22:31): - Attachment: #1341 colorBlindness > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jianhong/colorBlindness > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:40:37): Unknown User (15:26:59): - Attachment: #1342 ROCpAI > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/juanpegarcia/ROCpAI > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:30:20): - Attachment: #1343 DeMixT version changing > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:30:22): Unknown User (16:00:50): - Attachment: #1344 DeMixT > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wwylab/DeMixT > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > Hello Bioconductor Team, > > I am a new maintainer of DeMixT package. > > We aimed to release a new updated DeMixT package from version 1.3.1 to 1.5.0 in devel branch. > However, I got the following error message when I try to push the package public: > Error: Illegal version bump from ‘1.3.1’ to ‘1.5.0’. > > I am very confused about this issue, since I noticed that we need use odd number for y(x.y.z) in devel. How can I address this issue? > > Thanks, > Peng

Unknown User (16:00:52):

2020-01-16

Unknown User (09:26:52): - Attachment: #1345 reconsi > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/CenterForStatistics-UGent/reconsi > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-01-18

Unknown User (07:22:25): Unknown User (08:10:31):

2020-01-20

Unknown User (07:06:33):

2020-01-21

Unknown User (06:28:18):

2020-01-22

Unknown User (02:07:28): - Attachment: #1346 son.of.basilisk > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/LTLA/son.of.basilisk > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:36:06): Unknown User (16:23:04):

2020-01-23

Unknown User (08:51:27): - Attachment: #1347 GCSConnection > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Jiefei-Wang/GCSConnection > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:28:27): Unknown User (09:28:30):

2020-01-24

Unknown User (04:51:33): - Attachment: #1348 PeacoQC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/saeyslab/PeacoQC > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > Note: [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput cytometry data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-01-26

Unknown User (07:26:58): - Attachment: #1349 DAMEfinder > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/markrobinsonuzh/DAMEfinder > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (19:36:34): - Attachment: #1350 fluentGenomics > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/sa-lee/fluentGenomics > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-01-28

Unknown User (21:09:50): - Attachment: #1351 PloGO2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/APAFbioinformatics/PloGO2 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (21:09:52): Unknown User (21:11:58): - Attachment: #1352 PloGO2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/APAFbioinformatics/PloGO2 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-01-30

Unknown User (13:53:12): Unknown User (18:41:57): - Attachment: #1353 ctgPHYL > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bicbioeng/ctgPHYL > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-01-31

Unknown User (00:39:32): - Attachment: #1354 gmoviz > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/malhamdoosh/gmoviz > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:43:04): - Attachment: #1355 cerebroApp > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/romanhaa/cerebroApp > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:06:30):

2020-02-04

Unknown User (06:48:53): Unknown User (08:52:05): - Attachment: #1356 GeneTonic > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:52:07): Unknown User (08:53:22): - Attachment: #1357 GeneTonic > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/federicomarini/GeneTonic > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-02-05

Unknown User (17:20:48): Unknown User (17:20:51): Unknown User (17:20:52):

2020-02-06

Unknown User (02:27:01): - Attachment: #1358 metID: in-house MS2 database construction and metabolite identification package. > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jaspershen/metID > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (07:52:20): Unknown User (15:22:33): - Attachment: #1359 MiHC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:22:35): Unknown User (15:24:23): - Attachment: #1360 MiHC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:24:25):

2020-02-08

GitHub (Legacy) (01:18:59): > was added to this conversation

Sara Ballouz (05:52:16): > @Sara Ballouz has joined the channel

Unknown User (11:45:11): - Attachment: #1361 scTHI > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/miccec/scTHI > > Confirm the following by editing each check box to ‘[x]’ > > • [ X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ X] The ‘devel’ branch for new packages and features. > • [ ]X The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:46:31): - Attachment: #1362 scTHI.data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/miccec/scTHI.data > > Confirm the following by editing each check box to ‘[x]’ > > • [ X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ X] The ‘devel’ branch for new packages and features. > • [ X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:53:41):

2020-02-10

Unknown User (15:57:31): - Attachment: #1363 HIPPO > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > HIPPO_0.1.0.tar.gz

Unknown User (15:57:34): Unknown User (15:59:23): - Attachment: #1364 HIPPO > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/tk382/HIPPO > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:39:53): - Attachment: #1365 receptLoss > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/dpique/receptLoss > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-02-11

Unknown User (06:13:07): - Attachment: #1366 IntAssoPlot > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/whweve/IntAssoPlot > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:36:12): - Attachment: #1367 IntAssoPlot > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/whweve/IntAssoPlot > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:36:14): Unknown User (18:37:28): Unknown User (18:37:41):

2020-02-13

Unknown User (15:25:34): - Attachment: #1368 SynExtend > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/npcooley/Synextend > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:25:36): Unknown User (15:28:08): - Attachment: #1369 SynExtend > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/npcooley/SynExtend > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:58:39): - Attachment: #1370 SegmentedCellExperiment > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ellispatrick/SegmentedCellExperiment > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ X] The ‘devel’ branch for new packages and features. > • [ X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

FelixErnst (17:19:54): > @FelixErnst has joined the channel

2020-02-14

Unknown User (08:09:32): - Attachment: #1371 TADBD > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bioinfo-lab/TADBD > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:09:35): Unknown User (09:30:28): - Attachment: #1372 TADBD > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bioinfo-lab/TADBD > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:26:50): - Attachment: #1373 sarks > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/denniscwylie/sarks > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:30:43): Unknown User (15:30:44): Unknown User (15:30:47): Unknown User (15:30:48): Unknown User (15:30:50): Unknown User (15:30:53): Nicholas Cooley (16:19:18): > @Nicholas Cooley has joined the channel

2020-02-15

Unknown User (16:21:27): Unknown User (16:23:16): - Attachment: #1374 scDataviz: single cell dataviz and downstream analyses > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/kevinblighe/scDataviz > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-02-16

Unknown User (11:32:28): - Attachment: #1375 RNAAgeCalc > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/reese3928/RNAAgeCalc > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-02-18

Unknown User (04:35:57): - Attachment: #1376 DIscBIO > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ocbe-uio/DIscBIO > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-02-19

Unknown User (04:28:40): - Attachment: #1377 combi > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/CenterForStatistics-UGent/combi > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (22:28:22): - Attachment: #1378 grabsampling > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (22:28:24): Unknown User (22:29:44): - Attachment: #1379 https://github.com/Mayooran1987/grabsampling > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (22:29:45): Unknown User (22:31:37): - Attachment: #1380 grabsampling > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (22:31:39): Unknown User (22:33:42): - Attachment: #1381 grabsampling > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Mayooran1987/grabsampling > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-02-20

Unknown User (04:41:04): Unknown User (04:49:57): Unknown User (15:12:44):

2020-02-21

Unknown User (22:31:00): - Attachment: #1382 TAPseq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/argschwind/TAPseq > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-02-24

Unknown User (14:40:30): - Attachment: #1383 GPA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/carter-allen/GPA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (22:45:08): - Attachment: #1384 gpaExample > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/carter-allen/gpaExample > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (22:45:51):

2020-02-25

Unknown User (10:27:10): Unknown User (10:35:42): - Attachment: #1385 gpaExample > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/carter-allen/gpaExample > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:35:44): Unknown User (10:36:51): Unknown User (12:44:04): - Attachment: #1386 GGPA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/carter-allen/GGPA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:08:41): - Attachment: #1387 EpiTxDb > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/FelixErnst/EpiTxDb > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-02-26

Unknown User (02:17:42): - Attachment: #1388 rRPMM > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/afukushima/rRPMM > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (19:19:05): - Attachment: #1389 spatialLIBD > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/LieberInstitute/spatialLIBD > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-02-28

Unknown User (03:02:12): - Attachment: #1390 MicrobiotaProcess > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/YuLab-SMU/MicrobiotaProcess > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:25:34): - Attachment: #1391 rrvgo > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ssayols/rrvgo > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:30:47): - Attachment: #1392 ribosomeProfilingQC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jianhong/ribosomeProfilingQC > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-02-29

Unknown User (12:39:29): - Attachment: #1393 regutools > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ComunidadBioInfo/regutools > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-03-02

Unknown User (08:24:42): Unknown User (11:49:20): Unknown User (13:22:21): - Attachment: #1394 VaSP: Quantification and Visulization of Variations of Splicing in Population > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:22:23): Unknown User (15:06:26): - Attachment: #1395 JMP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/gitlzg/JMP > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:41:59): - Attachment: #1396 VaSP: Quantification and Visulization of Variations of Splicing in Population > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yuhuihui2011/VaSP > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:42:01): Unknown User (16:48:05): - Attachment: #1397 vasp > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yuhuihui2011/vasp > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (21:11:58): - Attachment: #1398 BRGenomics package contribution > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/mdeber/BRGenomics > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-03-03

Unknown User (13:32:29): Unknown User (14:02:40): - Attachment: #1399 vasp > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yuhuihui2011/vasp > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:02:42): Unknown User (14:49:42): - Attachment: #1400 Dune > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/HectorRDB/Dune > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:57:34): - Attachment: #1401 New package: svncvplus > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ccbiolab/svpluscnv > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:20:17): Unknown User (16:25:59): - Attachment: #1402 vasp > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yuhuihui2011/vasp > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:26:01): Unknown User (16:29:31): - Attachment: #1403 vasp > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yuhuihui2011/vasp > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:29:32): Unknown User (16:30:06): Unknown User (16:51:34): Unknown User (17:21:59): Unknown User (17:22:01): Unknown User (17:22:04): Unknown User (17:22:05): Unknown User (17:22:07): Unknown User (17:22:09):

2020-03-04

Unknown User (17:54:01): - Attachment: #1404 bioAnno > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/guokai8/bioAnno > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-03-05

Unknown User (03:33:32): - Attachment: #1405 generalKSStat > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Jiefei-Wang/generalKSStat > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-03-07

Unknown User (07:22:50): - Attachment: #1406 RegEnrich > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/WeiyangTao/RegEnrich > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (07:22:52): Unknown User (07:26:07): - Attachment: #1407 RegEnrich > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/WeiyangTao/RegEnrich > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:03:44): Unknown User (08:04:49): - Attachment: #1408 RegEnrich > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/WeiyangTao/RegEnrich > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:04:51): Unknown User (08:23:43): - Attachment: #1409 RegEnrich > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/WeiyangTao/RegEnrich > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:23:44): Unknown User (08:43:01): - Attachment: #1410 RegEnrich > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/WTaoUMC/RegEnrich > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:34:12): - Attachment: #1411 fmrs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/shokoohi/fmrs > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-03-08

Unknown User (07:35:04): - Attachment: #1412 scHOT > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/shazanfar/scHOT > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:49:48): Unknown User (15:49:50):

2020-03-09

Unknown User (14:13:51): - Attachment: #1413 BrainSABER > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bicbioeng/BrainSABER > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-03-10

Unknown User (08:26:32):

2020-03-11

Unknown User (11:05:48): - Attachment: #1414 GGPA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/carter-allen/GGPA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-03-12

Unknown User (21:54:38): - Attachment: #1415 CiteFuse > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/SydneyBioX/CiteFuse > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-03-13

Unknown User (02:58:26): - Attachment: #1416 test_biocon > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/BioAmelie/test_biocon.git > Confirm the following by editing each check box to ‘[x]’ > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (02:58:27): Unknown User (07:54:46): - Attachment: #1417 eisaR > • Repository: https://github.com/fmicompbio/eisaR > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > Remark: This is currently the case, except for an issue where the checker fails > to correctly interpret non-standard code evaluation, as in > BiocGenerics::subset(x, type = "exon"), where the checks fail due to > a “missing” variable type. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > Thank you!

2020-03-14

Unknown User (12:23:34): - Attachment: #1418 tensorICA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jinghan1018/tensorICA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:23:36): Unknown User (12:33:09): - Attachment: #1419 tensorICA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jinghan1018/tensorICA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-03-15

Unknown User (16:35:39): - Attachment: #1420 SCATE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/zji90/SCATE > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-03-17

Unknown User (00:49:43): - Attachment: #1421 weitrix > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/pfh/weitrix > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:05:29): - Attachment: #1422 scry > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/kstreet13/scry > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-03-18

Unknown User (13:37:23): - Attachment: #1423 rhdf5filters > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/grimbough/rhdf5filters/ > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (19:11:23): - Attachment: #1424 BiocDockerManager > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/nturaga/BiocDockerManager > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-03-19

Unknown User (04:17:30): - Attachment: #1425 iSEEu > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/iSEE/iSEEu > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:50:05): - Attachment: #1426 dpeak > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-03-20

Unknown User (09:39:06): Unknown User (10:40:16): - Attachment: #1427 dpeak > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/carter-allen/dpeak > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:04:37):

2020-03-22

Unknown User (08:27:16): - Attachment: #1428 CARNIVAL package initial submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/enio23/CARNIVAL > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:27:17): Unknown User (09:11:18): - Attachment: #1429 CARNIVAL > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/saezlab/CARNIVAL > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-03-23

Edgar (10:34:31): > @Edgar has joined the channel

Unknown User (11:29:01): - Attachment: #1430 methylSig > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/sartorlab/methylSig > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:51:45): - Attachment: #1431 glmGamPoi > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/const-ae/glmGamPoi > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Edgar (12:15:20): > @Edgar has left the channel

Unknown User (15:10:40): - Attachment: #1432 MsCoreUtils > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/RforMassSpectrometry/MsCoreUtils > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-03-24

Nitesh Turaga (09:05:36): > @Nitesh Turaga has left the channel

Unknown User (09:51:26): Unknown User (09:51:27): Unknown User (09:51:29): Unknown User (09:51:30): Unknown User (09:51:32): Unknown User (09:51:33): Unknown User (09:51:36): Unknown User (09:51:38): Unknown User (09:51:39): Unknown User (09:51:41): Unknown User (14:56:39): Unknown User (15:06:24): Unknown User (15:54:13): Unknown User (21:32:35): - Attachment: #1433 sangeranalyseR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/roblanf/sangeranalyseR > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-03-25

Unknown User (10:16:15): Unknown User (17:04:05): - Attachment: #1434 Submission of proBatch > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/symbioticMe/proBatch > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:04:07):

2020-03-26

Unknown User (08:15:12): Unknown User (11:23:45): Unknown User (11:24:11): Unknown User (11:29:15): Unknown User (11:29:17): Unknown User (12:03:17): - Attachment: #1435 New package submission - metaseqR2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/pmoulos/metaseqR2 > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:10:46): - Attachment: #1436 HighlyReplicatedRNASeq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/const-ae/HighlyReplicatedRNASeq > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:37:42): - Attachment: #1437 HIPPO > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/tk382/HIPPO > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:37:45):

2020-03-27

Unknown User (17:12:03): - Attachment: #1438 ExploreModelMatrix > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/csoneson/ExploreModelMatrix > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-03-29

Unknown User (11:47:00): - Attachment: #1439 bioconductor_docker_cetf > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/cbiagii/bioconductor_docker_cetf > > Confirm the following by editing each check box to ‘[x]’ > > • [ X ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ X ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ X ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ X ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ X ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ X ] The ‘devel’ branch for new packages and features. > • [ X ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ X ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:47:01):

2020-03-30

Unknown User (07:52:22): Unknown User (09:34:49): Unknown User (09:42:38): - Attachment: #1440 Sierra: new package for bioconductor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/VCCRI/Sierra > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:50:00): - Attachment: #1441 cytomapper > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/BodenmillerGroup/cytomapper > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:48:27): - Attachment: #1442 spqn > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hansenlab/spqn > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:58:10): Unknown User (15:06:26): - Attachment: #1443 spqnData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hansenlab/spqnData > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:31:27): - Attachment: #1444 TimeMeter R package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/pjiang1105/TimeMeter > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:54:55): Unknown User (18:54:57): Unknown User (18:54:59): Unknown User (19:38:17): - Attachment: #1445 CoreGx Package Submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bhklab/CoreGx > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (21:05:13): - Attachment: #1446 scClassify > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/SydneyBioX/scClassify > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (22:44:28): - Attachment: #1447 spicyR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ellispatrick/spicyR > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (23:53:36): - Attachment: #1448 MatrixGenerics > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor/MatrixGenerics > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-03-31

Unknown User (07:59:29): - Attachment: #1449 OpenStats > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/mpi2/impc_stats_pipeline/tree/master/Late%20adults%20stats%20pipeline/OpenStats/OpenStatsPackage > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (07:59:31): Unknown User (09:58:20): - Attachment: #1450 LACE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/BIMIB-DISCo/LACE > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:17:16): - Attachment: #1451 OpenStats > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/mpi2/OpenStats > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:29:56): - Attachment: #1452 timeOmics > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/abodein/timeOmics_BioC > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:29:59): Unknown User (16:12:14): - Attachment: #1453 timeOmics > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/abodein/timeOmics > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:28:40): Unknown User (18:42:25): Unknown User (18:42:26): Unknown User (21:31:13): - Attachment: #1454 TADCompare > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (21:31:14): Unknown User (21:32:38): - Attachment: #1455 TADCompare > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/cresswellkg/TADCompare > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (21:33:59): - Attachment: #1456 TADCompare > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/dozmorovlab/TADCompare > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (21:34:01):

2020-04-01

Unknown User (05:29:34): - Attachment: #1457 pipeComp > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/plger/pipeComp > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (07:31:31): Unknown User (09:29:01): Unknown User (19:52:14):

2020-04-02

Unknown User (05:22:28): - Attachment: #1458 discerner > • Repository: https://github.com/SimoneTiberi/discerner > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:37:49): - Attachment: #1459 mineMS2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/adelabriere/mineMS2 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:05:54): - Attachment: #1460 dorothea > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/saezlab/dorothea_R > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:05:55): Unknown User (17:46:46): - Attachment: #1461 moma.gbmexample > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/califano-lab/MOMA.gbmexample > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:46:48): Unknown User (17:48:45): - Attachment: #1462 moma.gbmexample > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/califano-lab/moma.gbmexample > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:54:48): - Attachment: #1463 TBSignatureProfiler > • Repository: https://github.com/compbiomed/TBSignatureProfiler > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor_ version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (21:34:42): - Attachment: #1464 SpiderSeqR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ss-lab-cancerunit/SpiderSeqR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-04-03

Unknown User (07:20:37): - Attachment: #1465 sparseMatrixStats > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/const-ae/sparseMatrixStats > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (07:35:51): - Attachment: #1466 dorothea > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/saezlab/dorothea > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:16:53): - Attachment: #1467 GWENA > Hello, > > I would like to submit the GWENA package for inclusion in BioConductor release 3.11. It is a package containing a pipeline for gene co-expression analysis with biological and topological tools for further analysis included. > > I hope you will find the package interesting enough to be included into Bioconductor. > > Regards, > Gwenaëlle > > ————————- > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Kumquatum/GWENA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:16:55): Unknown User (15:18:35): - Attachment: #1468 GWENA > Hello, > > I would like to submit the GWENA package for inclusion in BioConductor release 3.11. It is a package containing a pipeline for gene co-expression analysis with biological and topological tools for further analysis included. > > I hope you will find the package interesting enough to be included into Bioconductor. > > Regards, > Gwenaëlle > > ————————- > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Kumquatum/GWENA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:46:47): - Attachment: #1469 randRotation > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/phettegger/randRotation > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-04-04

Unknown User (16:48:05): - Attachment: #1470 SingleCellMultiModal > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/waldronlab/SingleCellMultiModal > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-04-05

Unknown User (15:33:21): - Attachment: #1471 ROSeq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/krishan57gupta/ROSeq > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:33:22):

2020-04-06

Unknown User (05:49:14): - Attachment: #1472 SPsimSeq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/CenterForStatistics-UGent/SPsimSeq > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:00:29): - Attachment: #1473 getDEE2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/markziemann/getDEE2 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:10:58): Unknown User (18:11:00): Unknown User (18:11:01): Unknown User (18:11:03):

2020-04-07

Unknown User (15:32:56): - Attachment: #1474 geneplast.data.string.v110 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/leofields/geneplast.data.string.v110 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:41:49): - Attachment: #1475 geneplast.data.orthodb.v101 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/leofields/geneplast.data.orthodb.v101 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:43:31): - Attachment: #1476 geneplast.data.oma.All.Jan2020 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:43:33): Unknown User (15:45:05): - Attachment: #1477 geneplast.data.oma.All.Jan2020 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/leofields/geneplast.data.oma.All.Jan2020 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:34:39): Unknown User (20:40:24): - Attachment: #1478 rfaRm > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/LaraSellesVidal/rfaRm > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-04-09

Unknown User (11:50:44): - Attachment: #1479 iCTC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/krishan57gupta/iCTC > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:22:21): Unknown User (14:08:02): Unknown User (14:08:18): Unknown User (14:08:33): Unknown User (14:08:34): Unknown User (14:09:17):

2020-04-12

Unknown User (11:16:29): Unknown User (11:16:32): Unknown User (11:16:33): Unknown User (11:16:35):

2020-04-14

Unknown User (06:56:04): - Attachment: #1480 MultiBaC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ConesaLab/MultiBaC.git > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (06:56:06): Unknown User (06:59:02): - Attachment: #1481 MultiBaC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ConesaLab/MultiBaC > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:21:04): Unknown User (13:21:06): Unknown User (13:21:07): Unknown User (13:21:09):

2020-04-15

Unknown User (06:58:32): - Attachment: #1482 uncoverappLib > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Manuelaio/uncoverappLib > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-04-16

Unknown User (08:15:31): Unknown User (11:45:38): Unknown User (11:45:39): Unknown User (11:45:41): Unknown User (11:45:43): Unknown User (13:51:49):

2020-04-17

Unknown User (05:35:29): Unknown User (05:35:30): Unknown User (05:35:32): Unknown User (05:35:33):

2020-04-20

Unknown User (07:11:53): - Attachment: #1483 Including multiGSEA in Bioconductor > • Repository: https://github.com/yigbt/multiGSEA > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-04-21

Unknown User (04:40:34): Unknown User (04:40:35): Unknown User (04:40:37): Unknown User (04:40:39): Unknown User (04:40:40): Unknown User (04:40:42): Unknown User (16:34:01): Unknown User (16:34:03): Unknown User (16:34:05): Unknown User (16:34:06): Unknown User (16:34:07): Unknown User (16:34:09): Unknown User (16:34:10):

2020-04-22

Unknown User (15:04:24): Unknown User (15:04:26): Unknown User (15:04:28): Unknown User (15:04:29): Unknown User (15:04:31): Unknown User (15:04:32): Unknown User (15:04:34): Unknown User (15:04:36): Unknown User (15:04:37): Unknown User (16:13:10): Unknown User (17:24:42): Unknown User (18:55:36): - Attachment: #1484 RadioGx resubmission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bhklab/RadioGx > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:55:38): Unknown User (18:58:32): - Attachment: #1485 ToxicoGx resubmission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bhklab/ToxicoGx > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:58:33):

2020-04-23

Unknown User (19:00:13): Unknown User (19:00:14): Unknown User (19:00:16): Unknown User (19:00:17):

2020-04-24

Unknown User (06:43:44): Unknown User (07:16:17): - Attachment: #1486 multicrispr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/loosolab/multicrispr > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-04-25

Unknown User (14:31:16): - Attachment: #1487 AnVIL > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor/AnVIL > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:50:41): - Attachment: #1488 cBioPortalData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/waldronlab/cBioPortalData > Confirm the following by editing each check box to ‘[x]’ > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:56:22): Unknown User (16:44:22): - Attachment: #1489 ToxicoGx Resubmission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bhklab/ToxicoGx > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:00:19): - Attachment: #1490 RadioGx resubmission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bhklab/RadioGx > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-04-26

Unknown User (14:08:35): Unknown User (14:08:43):

2020-04-27

Unknown User (09:43:29): Unknown User (12:25:56): - Attachment: #1491 Submit DegNorm R package to bioconductor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jipingw/DegNorm > > Confirm the following by editing each check box to ‘[x]’ > > • [ X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X ] The ‘devel’ branch for new packages and features. > • [X ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-04-28

Unknown User (09:12:14):

2020-05-01

Unknown User (02:30:08): - Attachment: #1492 corral > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/laurenhsu1/corral > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-05-04

Unknown User (06:46:45): - Attachment: #1493 simplifyEnrichment > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jokergoo/simplifyEnrichment > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-05-05

Unknown User (08:02:00):

2020-05-06

Unknown User (06:54:42): - Attachment: #1494 wpm > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/HelBor/wpm > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:29:50): Unknown User (13:29:52): Unknown User (19:46:12): - Attachment: #1495 scuttle > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/LTLA/scuttle > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-05-07

Unknown User (11:53:22): - Attachment: #1496 GSEAmining > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/oriolarques/GSEAmining > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-05-12

Unknown User (03:06:53): - Attachment: #1497 metaboliteIDmapping AnnotationHub package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yigbt/metaboliteIDmapping > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-05-14

Unknown User (14:59:06):

2020-05-15

Unknown User (00:19:42): - Attachment: #1498 hummingbird > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/eleniadam/hummingbird > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:37:59):

2020-05-18

Unknown User (16:12:51): Unknown User (16:12:52): Unknown User (16:12:54):

2020-05-20

Unknown User (13:55:43):

2020-05-21

Unknown User (09:37:38): Unknown User (10:10:54): - Attachment: #1499 MouseFM > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/matmu/MouseFM > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:44:05): - Attachment: #1500 Submit R package CNVtest > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wuqian77/CNVtest > > Confirm the following by editing each check box to ‘[x]’ > > • [X ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X ] The ‘devel’ branch for new packages and features. > • [X ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-05-22

Unknown User (15:00:17):

2020-05-24

Unknown User (02:00:38): - Attachment: #1501 CytoTree > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/JhuangLab/CytoTree > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-05-25

Unknown User (12:30:46): - Attachment: #1502 GenomicDistributions submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/databio/GenomicDistributions > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-05-26

Unknown User (07:33:59): - Attachment: #1503 scRepertoire submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ncborcherding/scRepertoire > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-05-27

Unknown User (06:50:05): - Attachment: #1504 UMI4Cats package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Pasquali-lab/UMI4Cats > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-05-28

Unknown User (10:35:25):

2020-05-30

Unknown User (16:55:00):

2020-06-01

Unknown User (17:56:46): Unknown User (17:56:48): Unknown User (17:56:49): Unknown User (17:56:51): Unknown User (17:56:52): Unknown User (17:56:54): Unknown User (17:56:55): Unknown User (17:56:57): Unknown User (17:56:58):

2020-06-02

Unknown User (13:26:46): - Attachment: #1505 MAUDE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Carldeboer/MAUDE > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-06-03

Unknown User (10:00:04): - Attachment: #1506 TEnGExA: Tissue-Enrichment and Gene Expression Analysis Tool > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hcrawal/TEnGExA_1.0 > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:00:06): Unknown User (11:24:08): - Attachment: #1507 Omixer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/molepi/Omixer > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > However, since my package relies on setting multiple seeds to create > different but randomized sample layouts, there is 1 (unavoidable) WARNING > on R CMD BiocCheck. I would very much appreciate discussion of this. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-06-05

Unknown User (09:41:05): - Attachment: #1508 Rtpca > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/nkurzaw/Rtpca > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-06-06

Olagunju Abdulrahman (19:57:39): > @Olagunju Abdulrahman has joined the channel

2020-06-08

Unknown User (20:29:31): Unknown User (20:29:37): Unknown User (23:54:30): - Attachment: #1509 scCB2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/zijianni/scCB2 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-06-10

Unknown User (13:33:07): - Attachment: #1510 escape Submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ncborcherding/escape > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-06-11

Unknown User (13:07:45): - Attachment: #1511 periodicDNA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/js2264/periodicDNA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-06-12

Unknown User (06:08:23): - Attachment: #1512 padma > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/andreamrau/padma > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:59:38): - Attachment: #1513 transomics2cytoscape > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ecell/transomics2cytoscape > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:30:58): Unknown User (15:32:10): Unknown User (15:32:11): Unknown User (15:32:13): Unknown User (15:32:14): Unknown User (15:32:16): Unknown User (15:32:18): Unknown User (16:21:49): - Attachment: #1514 fmrs package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/shokoohi/fmrs > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:21:51): Unknown User (16:28:55):

2020-06-13

Unknown User (04:11:03): - Attachment: #1515 celldex > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/LTLA/celldex > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (06:07:44): Unknown User (06:26:44): - Attachment: #1516 MesKit > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Niinleslie/MesKit > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-06-14

Unknown User (08:36:49): - Attachment: #1517 SplicingFactory > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/SU-CompBio/SplicingFactory > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor [Package Submission][2] > instructions. My package is consistent with the Bioconductor > [Package Guidelines][1]. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the [support site][3] for issues that users may > have, subscribing to the [bioc-devel][4] mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using [Git][5] > (optionally [via GitHub][6]). > > For help with submitting your package, please subscribe and post questions > to the [bioc-devel][4] mailing list.

2020-06-16

Unknown User (00:43:19):

2020-06-17

Unknown User (09:40:59): - Attachment: #1518 Submit test-package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/test-bioc/test-package > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:41:03): Unknown User (09:44:35): - Attachment: #1519 test-package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/test-bioc/test-package > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:44:38): Unknown User (10:06:07): - Attachment: #1520 test-package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/test-bioc/test-package > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:06:10): Unknown User (10:10:07): - Attachment: #1521 test-package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/test-bioc/test-package > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:10:09): Unknown User (10:17:28): - Attachment: #1522 Submit test-package1 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/test-bioc/test-package1 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:17:46):

2020-06-18

Unknown User (00:56:11): - Attachment: #1523 RIPAT > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bioinfo16/RIPAT > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (05:47:58): Unknown User (12:30:14): - Attachment: #1524 POMA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/pcastellanoescuder/POMA > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-06-19

Unknown User (03:39:24): - Attachment: #1525 Submission of package infinityFlow > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ebecht/infinityFlow > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (03:39:27): Unknown User (03:47:03): - Attachment: #1526 Submission of package infinityFlow > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ebecht/infinityFlow > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:20:57):

2020-06-20

Unknown User (16:08:55): - Attachment: #1527 recountmethylation > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/metamaden/recountmethylation > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-06-21

Unknown User (16:22:06): - Attachment: #1528 monaR > • Repository: https://github.com/gjgetzinger/monaR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor [Package Submission][2] > instructions. My package is consistent with the Bioconductor > [Package Guidelines][1]. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the [support site][3] for issues that users may > have, subscribing to the [bioc-devel][4] mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using [Git][5] > (optionally [via GitHub][6]).

2020-06-22

Unknown User (16:52:09): - Attachment: #1529 TMExplorer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/shooshtarilab/TMExplorer > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:52:11): Unknown User (17:02:55): - Attachment: #1530 TMExplorer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/shooshtarilab/TMExplorer > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:02:57):

2020-06-24

Unknown User (10:18:04): - Attachment: #1531 Submit test-package - this should be closed automatically > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/turaganitesh/test-package > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:26:56): Unknown User (10:30:17): - Attachment: #1532 Submit test-package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/turaganitesh/test-package > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:30:19): Unknown User (12:01:29): - Attachment: #1533 TMExplorer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/shooshtarilab/TMExplorer > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-06-26

Unknown User (10:12:10): - Attachment: #1534 ILoReg R package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/elolab/iloreg > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:12:12): Unknown User (10:26:48): - Attachment: #1535 ILoReg R package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/elolab/ILoReg > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:26:51): Unknown User (10:34:06): - Attachment: #1536 ILoReg R package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/elolab/ILoReg > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-06-29

Unknown User (11:49:14): Unknown User (11:49:28): Unknown User (21:33:15): - Attachment: #1537 PhosR > • Repository: https://github.com/PYangLab/PhosR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor [Package Submission][2] > instructions. My package is consistent with the Bioconductor > [Package Guidelines][1]. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the [support site][3] for issues that users may > have, subscribing to the [bioc-devel][4] mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using [Git][5] > (optionally [via GitHub][6]).

Unknown User (21:33:17): Unknown User (21:42:57): - Attachment: #1538 PhosR > • Repository: https://github.com/PYangLab/PhosR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor [Package Submission][2] > instructions. My package is consistent with the Bioconductor > [Package Guidelines][1]. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the [support site][3] for issues that users may > have, subscribing to the [bioc-devel][4] mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using [Git][5] > (optionally [via GitHub][6]).

2020-06-30

Unknown User (10:41:45): - Attachment: #1539 MetaGSCA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:41:47):

2020-07-01

Unknown User (11:27:41): - Attachment: #1540 test-package 1 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/turaganitesh/test-package > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-07-02

Unknown User (10:47:49):

2020-07-03

Unknown User (14:04:37): - Attachment: #1541 Submit testbiocpackage1234 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/turaganitesh/testbiocpackage1234 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (22:07:29): - Attachment: #1542 geneplast.data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/leofields/geneplast.data > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-07-07

Unknown User (06:36:52): Unknown User (06:37:21): - Attachment: #1543 update to reflect new package work flow > • package added at start of review process > • pushes to git.bioconductor.org > • no need for user-applied web hook > • update AdditionalPackage workflow

Unknown User (11:18:38): - Attachment: #1544 SpatialExperiment > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/drighelli/SpatialExperiment > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:24:24): Unknown User (14:20:46): - Attachment: #1545 clustifyrdatahub > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/rnabioco/clustifyrdatahub > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:49:19): - Attachment: #1546 BiocIO > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor/BiocIO > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:25:45): Unknown User (15:42:39): Unknown User (15:42:41):

2020-07-08

Unknown User (09:06:53): Unknown User (09:06:54): Unknown User (10:08:17): - Attachment: #1547 VplotR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/js2264/VplotR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-07-09

Unknown User (19:47:52): Unknown User (19:47:54): Unknown User (19:47:55): Unknown User (19:47:56):

2020-07-10

Unknown User (07:38:42): - Attachment: #1548 SeqGate > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/srialle/SeqGate > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:24:17): - Attachment: #1549 zellkonverter > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/theislab/zellkonverter > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-07-13

Unknown User (04:25:16): - Attachment: #1550 ggtreeExtra > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/YuLab-SMU/ggtreeExtra > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:31:32): - Attachment: #1551 Submitting new R package, preciseTAD, to Bioconductor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/dozmorovlab/preciseTAD > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:31:33): Unknown User (17:35:51): - Attachment: #1552 New package: preciseTAD > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/dozmorovlab/preciseTAD > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:35:53):

2020-07-14

Unknown User (10:59:44): - Attachment: #1553 New package: preciseTAD > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/dozmorovlab/preciseTAD > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:04:34): - Attachment: #1554 FieldEffectCrc > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/BarcUVa-Seq/FieldEffectCrc > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-07-15

Unknown User (13:08:01): - Attachment: #1555 timecoursedata > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/nellev/timecoursedata > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-07-16

Unknown User (06:34:05): - Attachment: #1556 QFeatures > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/rformassspectrometry/QFeatures > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-07-17

Unknown User (15:22:31): - Attachment: #1557 miRDriver > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bozdaglab/miRDriver > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:22:33): Unknown User (15:49:27): - Attachment: #1558 miRDriver > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:49:29): Unknown User (15:50:09): - Attachment: #1559 miRDriver > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bozdaglab/miRDriver > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:50:12): Unknown User (15:53:16): - Attachment: #1560 miRDriver > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bozdaglab/miRDriver > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:53:18): Unknown User (16:00:21): - Attachment: #1561 miRDriver > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bozdaglab/miRDriver > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:00:23): Unknown User (16:03:29): - Attachment: #1562 miRDriver > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bozdaglab/miRDriver > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:03:31): Unknown User (16:09:03): - Attachment: #1563 miRDriver > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bozdaglab/miRDriver > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-07-19

Unknown User (06:51:13): - Attachment: #1564 bluster > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/LTLA/bluster > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-07-21

Unknown User (05:58:48): Unknown User (09:25:36): Unknown User (10:31:42): - Attachment: #1565 snifter > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Alanocallaghan/snifter > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:51:36): Unknown User (13:53:49): Unknown User (16:19:03): - Attachment: #1566 HPAStainR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/tnieuwe/HPAStainR_package > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:17:29): Unknown User (17:21:16):

2020-07-24

Isha Goel (07:47:10): > @Isha Goel has joined the channel

2020-07-28

Unknown User (03:09:53): - Attachment: #1567 Nebulosa > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/powellgenomicslab/Nebulosa > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:47:45): - Attachment: #1568 MetaGSCA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Haocan223/MetaGSCA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:10:59): - Attachment: #1569 Package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/vbusa1/nearBynding > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-07-29

Unknown User (09:10:36): - Attachment: #1570 HMMRATAC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor/HMMRATAC > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:28:31): Unknown User (09:47:46): - Attachment: #1571 HPAStainR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/tnieuwe/HPAStainR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:28:23): - Attachment: #1572 PhenoGeneRanker Submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bozdaglab/PhenoGeneRankerPackage > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (16:28:24): Riyue Sunny Bao (17:38:31): > @Riyue Sunny Bao has joined the channel

Unknown User (18:59:50): - Attachment: #1573 PhenoGeneRanker Package Submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bozdaglab/PhenoGeneRankerPackage > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (18:59:52): Unknown User (19:02:43): - Attachment: #1574 PhenoGeneRanker > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bozdaglab/PhenoGeneRankerPackage > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (19:02:46):

2020-07-30

Unknown User (05:36:47): - Attachment: #1575 ncRNAtools > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/LaraSellesVidal/ncRNAtools > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:15:55): Unknown User (09:15:57): Unknown User (12:10:06): - Attachment: #1576 PhenoGeneRanker > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bozdaglab/PhenoGeneRanker > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Ayush Raman (12:43:51): > @Ayush Raman has joined the channel

2020-07-31

Unknown User (08:29:10): - Attachment: #1577 metabolomicsWorkbenchR: An R package for interfacing with the Metabolomics Workbench API > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/computational-metabolomics/metabolomicsWorkbenchR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-08-02

Unknown User (05:48:19): - Attachment: #1578 Submit a new package “BP4RNAseq” > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/sunshanwen/BP4RNAseq > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (05:48:22): Unknown User (07:02:54): Unknown User (07:03:05):

2020-08-03

Unknown User (08:48:26): - Attachment: #1579 ERROR in read_cisbp > Hi, I want to convert CIS-BP’s motif format to meme format. > the first step, I downloaded the pwm data from http://cisbp.ccbr.utoronto.ca/bulk.php. > then I chose one pwm file as input for read_cisbp, just list this, data <- read_cisbp("M00008_2.00.txt"), but unfortunately I got an error message,Error in mapply(function(x, y) raw_lines[x:y], meta_starts, meta_stops, :zero-length inputs cannot be mixed with those of non-zero length. > I don’t what the reason is. I have tried read_meme() function, where the input file download from jaspar website, and this time it can be loaded successfully. So I think my system and R version and so on are ok. > How can I convert CIS-BP’s motif data to meme format? > Thank you very much.

Unknown User (08:48:27): Unknown User (16:14:21): Unknown User (16:14:22):

2020-08-04

Unknown User (18:43:59): - Attachment: #1580 Rfastp > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/RockefellerUniversity/Rfastp > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-08-06

Unknown User (05:16:11): - Attachment: #1581 BP4RNAseq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/sunshanwen/BP4RNAseq > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-08-07

Unknown User (10:07:50): Unknown User (10:09:01): - Attachment: #1582 Rfastp > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/RockefellerUniversity/Rfastp > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:09:03): Unknown User (10:10:35): - Attachment: #1583 package Rfastp > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/RockefellerUniversity/Rfastp > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:10:37): Unknown User (10:12:15):

2020-08-09

Unknown User (10:42:50): - Attachment: #1584 Informeasure > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/chupan1218/Informeasure > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-08-10

Unknown User (10:53:46): - Attachment: #1585 ISAnalytics > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/calabrialab/ISAnalytics > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:49:31): - Attachment: #1586 ANCOMBC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/FrederickHuangLin/ANCOMBC > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:01:12): Unknown User (13:01:14): Unknown User (13:01:49): Unknown User (14:09:42): - Attachment: #1587 MicrobiomeExplorer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/zoecastillo/microbiomeExplorer > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-08-11

Unknown User (09:16:03): - Attachment: #1588 subHMM > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wheelerb/subHMM > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:16:05): Unknown User (09:37:58): - Attachment: #1589 subHMM > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wheelerb/subHMM > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-08-12

Unknown User (01:45:57): - Attachment: #1590 rebook > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/LTLA/rebook > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-08-13

Unknown User (05:08:29): - Attachment: #1591 SCFA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/duct317/SCFA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (13:32:27): Unknown User (13:32:28): Unknown User (13:32:30): Unknown User (13:32:32): Unknown User (13:33:12):

2020-08-15

Unknown User (19:17:57): - Attachment: #1592 FScanR: an R package to detect Programmed Ribosomal Frameshifting (PRF) events from mRNA/cDNA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/seanchen607/FScanR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (19:17:59): Unknown User (19:29:54): - Attachment: #1593 FScanR: an R package to detect Programmed Ribosomal Frameshifting (PRF) events from mRNA/cDNA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/seanchen607/FScanR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-08-16

Unknown User (17:02:40): - Attachment: #1594 rsemmed > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/lmyint/rsemmed > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-08-17

Unknown User (22:12:09): - Attachment: #1595 bambu > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/GoekeLab/bambu > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (22:12:11): Unknown User (22:24:26): - Attachment: #1596 bambu > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/GoekeLab/bambu > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-08-18

Unknown User (07:39:05): Unknown User (07:40:06): Unknown User (07:54:11):

2020-08-19

Unknown User (14:38:49): Unknown User (14:38:51): Unknown User (14:40:30):

2020-08-20

Unknown User (02:25:07): - Attachment: #1597 DropletTestFiles > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/LTLA/DropletTestFiles > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (06:26:25): - Attachment: #1598 AlpsNMR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/sipss/AlpsNMR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (07:26:06): - Attachment: #1599 FilterFFPE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/LanyingWei/FilterFFPE > Confirm the following by editing each check box to ‘[x]’ > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:33:23): - Attachment: #1600 idpr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wmm27/idpr > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-08-22

Unknown User (05:02:27): - Attachment: #1601 proActiv > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/GoekeLab/proActiv > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (05:02:28): Unknown User (05:15:48): - Attachment: #1602 proActiv > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/GoekeLab/proActiv > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-08-23

Unknown User (02:37:46): - Attachment: #1603 revise and upgrade sparsenetgls to version 2.0 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/superOmics/sparsenetgls > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (02:37:48): Unknown User (02:54:58): - Attachment: #1604 upgrade sparsenetgls to version 2.0 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/superOmics/sparsenetgls > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (02:55:00): Unknown User (09:50:33): - Attachment: #1605 msImpute > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/DavisLaboratory/msImpute > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (09:50:35): Unknown User (10:15:07): - Attachment: #1606 msImpute > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/DavisLaboratory/msImpute > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:15:49): Unknown User (17:18:54): Unknown User (17:32:57): Unknown User (17:32:59): Unknown User (18:22:44):

2020-08-24

Evgeniy Rumynskiy (05:41:45): > @Evgeniy Rumynskiy has joined the channel

Unknown User (14:27:13): Unknown User (14:27:14): Unknown User (14:27:16):

2020-08-25

Unknown User (00:02:39): - Attachment: #1607 OrchestratingSingleCellAnalysisWrapper > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/LTLA/OrchestratingSingleCellAnalysisWrapper > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:30:54): - Attachment: #1608 CTDPathSim > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/bozdaglab/CTDPathSim > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-08-26

Unknown User (01:06:00): - Attachment: #1609 SingleRBookWrapper > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/LTLA/SingleRBookWrapper > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-08-27

Unknown User (10:16:04): - Attachment: #1610 MOGAMUN > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/elvanov/MOGAMUN > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:16:36): Unknown User (14:16:38): Unknown User (14:16:40):

2020-08-28

Unknown User (08:24:13):

2020-08-29

Unknown User (20:49:01): - Attachment: #1611 Update of tidybulk > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/stemangiola/tidybulk > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (20:49:04):

2020-08-30

Unknown User (22:51:00): - Attachment: #1612 ResidualMatrix > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/LTLA/ResidualMatrix > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-08-31

Unknown User (11:37:57): - Attachment: #1613 MethReg > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/TransBioInfoLab/MethReg > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-09-01

Unknown User (01:52:02): - Attachment: #1614 Spectra package for representation and analysis of mass spectrometry data > Dear BioC core, > > with this we (Laurent Gatto, Sebastian Gibb and myself) would like to submit the Spectra package for representation and analysis of mass spectrometry data to Bioconductor. I’d also like to clarify some issues thrown by BiocCheck: > • Check of page documentation: the man page of MsBackend.Rd does not have runnable examples because MsBackend is a virtual class and this man page just describes the API. > • We use the email address maintainer@rformassspectrometry.org as maintainer email which is not registered at the support site - emails to this address get automatically forwarded to Laurent, Sebastian and myself (we have the same address also for the MsCoreUtils package. > > We thank you in advance for revising and checking our package! > > Best regards, Johannes > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/RforMassSpectrometry/Spectra > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (02:43:45): - Attachment: #1615 tidySCE - brings SingleCellExperiment to tidyverse with no side effects > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/stemangiola/tidySCE > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (08:41:39): - Attachment: #1616 GSgalgoR: Identification and Study of Prognostic Gene Expression Signatures in Cancer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/harpomaxx/GSgalgoR/ > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-09-02

Unknown User (02:49:56): - Attachment: #1617 moanin: An R Package for Time Course RNASeq Data Analysis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/NelleV/moanin > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (10:22:31): - Attachment: #1618 cellmigRation > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ocbe-uio/cellmigRation > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:55:49): - Attachment: #1619 pageRank > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hd2326/pageRank > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-09-03

Unknown User (07:20:51): - Attachment: #1620 ORFhunteR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/rfctbio-bsu/ORFhunteR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:13:19): - Attachment: #1621 aggregateBioVar > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jasonratcliff/aggregateBioVar > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:29:58): Unknown User (14:31:01): Unknown User (14:31:02): Unknown User (14:31:04): Unknown User (14:31:05): Unknown User (17:34:16): - Attachment: #1622 CellaRepertorium: data structures and statistical analysis for SC immune repertoires > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/amcdavid/CellaRepertorium > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-09-05

Unknown User (18:10:13): - Attachment: #1623 LRcell > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/marvinquiet/LRcell > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-09-06

Unknown User (19:01:10): - Attachment: #1624 BayesSpace > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/edward130603/BayesSpace > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-09-07

Unknown User (11:10:52): - Attachment: #1625 OBIF > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/evanslaboratory/obif > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:10:54): Unknown User (11:15:40): - Attachment: #1626 OBIF > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/evanslaboratory/OBIF > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:15:43): Unknown User (11:28:22): - Attachment: #1627 OBIF > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/evanslaboratory/OBIF > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-09-08

Unknown User (03:44:58): - Attachment: #1628 scp: Utility functions for manipulating, processing, and analyzing mass spectrometry-based single-cell proteomics data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/UCLouvain-CBIO/scp > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > monts, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (04:25:18): - Attachment: #1629 NewWave > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/fedeago/NewWave > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (15:19:12): Unknown User (15:19:59): Unknown User (15:21:54): Unknown User (15:41:53):

2020-09-09

Unknown User (01:15:30): - Attachment: #1630 CTD > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/BRL-BCM/CTD > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (04:14:52):

2020-09-10

Unknown User (19:16:20): - Attachment: #1631 tidySE - brings SummarizedExperiment to tidyverse with no side effects > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/stemangiola/tidySE > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-09-11

Unknown User (05:34:48): - Attachment: #1632 velociraptor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/kevinrue/velociraptor > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (14:32:25): Unknown User (14:43:40): Unknown User (14:43:43):

2020-09-13

Unknown User (00:42:21): - Attachment: #1633 metabCombiner > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hhabra/metabCombiner > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [?] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (17:05:05): - Attachment: #1634 TileDBArray > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/LTLA/TileDBArray > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-09-14

Unknown User (08:37:45):

2020-09-15

Unknown User (10:18:04): - Attachment: #1635 tomoda > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/liuwd15/tomoda > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:29:08): Unknown User (12:30:06): Unknown User (12:31:17): Unknown User (12:35:32): Unknown User (12:35:56): Unknown User (12:40:34): Unknown User (13:54:39): Unknown User (17:15:45): Unknown User (17:15:46): Unknown User (17:15:49): Unknown User (17:16:19): Unknown User (17:16:20):

2020-09-16

Unknown User (11:26:45): - Attachment: #1636 GCSFilesystem > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Jiefei-Wang/GCSFilesystem > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (11:26:47): Ben Story (11:27:47): > @Ben Story has joined the channel

Unknown User (11:29:10): - Attachment: #1637 GCSFilesystem > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Jiefei-Wang/GCSFilesystem > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (12:53:19): Unknown User (12:53:29): Unknown User (12:53:50): Unknown User (12:54:11): Unknown User (12:57:14): Unknown User (12:57:22): Unknown User (13:10:39):

2020-09-17

Unknown User (12:44:49):

2020-09-21

Unknown User (16:52:50): Unknown User (16:52:53): Unknown User (16:52:55): Unknown User (16:52:56): Unknown User (16:52:59): Unknown User (16:52:59): Belinda Phipson (20:19:34): > @Belinda Phipson has joined the channel

Unknown User (23:54:11): - Attachment: #1638 spatialHeatmap > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jianhaizhang/spatialHeatmap > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

Unknown User (23:54:12): Unknown User (23:58:31): - Attachment: #1639 spatialHeatmap > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jianhaizhang/spatialHeatmap > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list.

2020-09-24

Unknown User (10:16:00): - Attachment: #1640 ChromSCape: analysis of single-cell epigenomic data in a Shiny App > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/vallotlab/ChromSCape > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (10:16:02): Unknown User (10:20:58): - Attachment: #1641 ChromSCape: Analysis of single-cell epigenomic data in a Shiny App > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/vallotlab/ChromSCape > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (10:20:59): Unknown User (10:25:54): - Attachment: #1642 ChromSCape: Analysis of single-cell epigenomic data in a Shiny App > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/vallotlab/ChromSCape > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

2020-09-25

Unknown User (15:33:43): Unknown User (15:33:45): Unknown User (15:33:46): Unknown User (15:33:48): Unknown User (15:33:50): Unknown User (15:33:52): Unknown User (17:43:50): - Attachment: #1643 densvis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Alanocallaghan/densvis > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

2020-09-26

Unknown User (13:05:07): - Attachment: #1644 rnaEditr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/TransBioInfoLab/rnaEditr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (14:33:51): Unknown User (14:34:20): Unknown User (14:34:49):

2020-09-27

Unknown User (22:36:33): - Attachment: #1645 NanoMethViz > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/shians/nanomethviz > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (22:36:35): Unknown User (22:37:19): - Attachment: #1646 NanoMethViz > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/shians/NanoMethViz > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (22:37:19): Unknown User (22:38:36): - Attachment: #1647 NanoMethViz > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/shians/NanoMethViz > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

2020-09-28

Unknown User (23:57:38): - Attachment: #1648 MSstatsPTM > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tsunghengtsai/MSstatsPTM > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (23:57:40):

2020-09-29

Unknown User (00:27:58): - Attachment: #1649 MSstatsPTM > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tsunghengtsai/MSstatsPTM > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

2020-09-30

Unknown User (07:48:48): - Attachment: #1650 octad > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/octad > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (07:48:50): Unknown User (07:51:34): - Attachment: #1651 octad > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Bin-Chen-Lab/octad_desktop > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (07:51:36): Unknown User (09:55:33): - Attachment: #1652 ttgsea > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/dongminjung/ttgsea > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (14:25:39): - Attachment: #1653 ADImpute > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/anacarolinaleote/ADImpute > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (14:25:41): Unknown User (15:29:59): - Attachment: #1654 Herper > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/RockefellerUniversity/Herper > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (17:01:58): - Attachment: #1655 ADImpute > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/anacarolinaleote/ADImpute > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (17:40:21): - Attachment: #1656 Famat > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/emiliesecherre/famat > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (21:31:18): - Attachment: #1657 AnVILBilling > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/vjcitn/AnVILBilling > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (21:31:20): Unknown User (21:31:21): Unknown User (21:32:56): Unknown User (21:34:19): - Attachment: #1658 AnVILBilling > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/vjcitn/AnVILBilling > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (21:34:21): Unknown User (21:34:23): Unknown User (21:36:33): Unknown User (21:38:16): - Attachment: #1659 AnVILBilling package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/vjcitn/AnVILBilling > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (22:46:38): - Attachment: #1660 systemPipeShiny > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/systemPipeR/systemPipeShiny > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

2020-10-01

Unknown User (02:17:58): - Attachment: #1661 MOFA2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/bioFAM/MOFA2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (05:18:28): - Attachment: #1662 PFP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (05:18:30): Unknown User (11:02:01): - Attachment: #1663 MSstatsConvert package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Vitek-Lab/MSstatsConvert > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (11:02:03): Unknown User (11:04:43): - Attachment: #1664 MSstatsConvert package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Vitek-Lab/MSstatsConvert > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (11:58:20): - Attachment: #1665 PFP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/aib-group/PFP > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (11:58:22): Unknown User (12:20:57): - Attachment: #1666 PFP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/aib-group/PFP > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (12:21:00): Unknown User (12:24:06): - Attachment: #1667 PFP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/aib-group/PFP > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (12:24:07): Unknown User (12:34:46): - Attachment: #1668 VERSO package > • Repository: https://github.com/BIMIB-DISCo/VERSO > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (12:47:19): - Attachment: #1669 PFP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/aib-group/PFP > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (13:15:10): - Attachment: #1670 MSEADbi > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/biopackathon/MSEADbi > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (15:51:38): - Attachment: #1671 AnVILPublish > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mtmorgan/AnVILPublish > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (16:42:12): - Attachment: #1672 ExperimentSubset > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/campbio/ExperimentSubset > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (16:42:15): Unknown User (16:54:01): - Attachment: #1673 ExperimentSubset > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/campbio/ExperimentSubset > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (17:21:14): Unknown User (17:21:41): Unknown User (18:53:47): - Attachment: #1674 biocthis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lcolladotor/biocthis > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. Note: it enables creating more packages. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (20:33:00): - Attachment: #1675 MethylSeqData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/PeteHaitch/MethylSeqData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (20:58:38): - Attachment: #1676 MSstatsTMTPTM > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Vitek-Lab/MSstatsTMTPTM > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (20:58:42): Unknown User (21:09:08): - Attachment: #1677 MSstatsTMTPTM > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Vitek-Lab/MSstatsTMTPTM > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (22:07:46): - Attachment: #1678 octad > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Bin-Chen-Lab/octad > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (22:07:47): Unknown User (22:30:55): - Attachment: #1679 octad > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Bin-Chen-Lab/octad > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

2020-10-02

Unknown User (01:53:13): - Attachment: #1680 customCMPdb > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yduan004/customCMPdb > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (03:56:52): Unknown User (03:58:09): - Attachment: #1681 VERSO package > • Repository: https://github.com/BIMIB-DISCo/VERSO > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (03:58:11): Unknown User (04:00:53): - Attachment: #1682 VERSO > • Repository: https://github.com/BIMIB-DISCo/VERSO > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (04:00:54): Unknown User (04:02:38): Unknown User (04:34:25): - Attachment: #1683 CNVgears > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SinomeM/CNVgears > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (04:34:27): Unknown User (04:37:16): - Attachment: #1684 CNVgears > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SinomeM/CNVgears > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (04:37:17): Unknown User (04:43:18): - Attachment: #1685 CNVgears > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SinomeM/CNVgears > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (07:17:29): - Attachment: #1686 VERSO package > • Repository: https://github.com/BIMIB-DISCo/VERSOe > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (07:17:30): Unknown User (07:19:27): - Attachment: #1687 VERSO package > • Repository: https://github.com/BIMIB-DISCo/VERSO > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (07:19:30): Unknown User (08:33:20): - Attachment: #1688 VERSO package > • Repository: https://github.com/BIMIB-DISCo/VERSO > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (08:33:23): Unknown User (10:00:08): Unknown User (11:10:08): - Attachment: #1689 VERSO > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BIMIB-DISCo/VERSO > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (11:48:50): - Attachment: #1690 SpatialDecon > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Nanostring-Biostats/SpatialDecon > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (12:39:37): - Attachment: #1691 recount3 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/LieberInstitute/recount3 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (14:13:17): - Attachment: #1692 marr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Ghoshlab/marr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (14:45:27): - Attachment: #1693 lefser > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/waldronlab/lefser > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (14:45:30): Unknown User (14:59:12): - Attachment: #1694 MSPrep > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/KechrisLab/MSPrep > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (15:44:41): - Attachment: #1695 lefser > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/waldronlab/lefser > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (15:51:08): - Attachment: #1696 megadepth > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/LieberInstitute/megadepth > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (16:53:46): - Attachment: #1697 SpiderSeqR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ss-lab-cancerunit/SpiderSeqR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (16:53:48): Unknown User (16:59:49): Unknown User (17:08:29): - Attachment: #1698 SpiderSeqR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ss-lab-cancerunit/SpiderSeqR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (17:08:31): Unknown User (17:11:13): - Attachment: #1699 SpiderSeqR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ss-lab-cancerunit/SpiderSeqR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (17:11:15): Unknown User (18:53:47): - Attachment: #1700 musicatk > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/campbio/musicatk > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (18:53:49): Unknown User (18:57:05): - Attachment: #1701 musicatk > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/campbio/musicatk > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (22:22:52): - Attachment: #1702 flowGraph > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/aya49/flowGraph > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (22:22:54): Unknown User (22:33:40): - Attachment: #1703 flowGraph > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/aya49/flowGraph > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

2020-10-04

Unknown User (21:44:29): Unknown User (21:44:31):

2020-10-05

Unknown User (14:05:25): - Attachment: #1704 GWAS.BAYES > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/marf-at-vt/GWAS.BAYES > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (14:05:27): Unknown User (14:26:48): - Attachment: #1705 GWAS.BAYES > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/marf-at-vt/GWAS.BAYES > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (17:12:54): - Attachment: #1706 cfDNAPro > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/hw538/cfDNAPro > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

2020-10-06

Unknown User (13:19:50): Unknown User (13:19:52): Unknown User (13:19:53):

2020-10-08

Unknown User (18:06:00): Unknown User (18:16:56): Unknown User (18:16:57):

2020-10-09

Unknown User (10:13:30): Unknown User (11:15:45): - Attachment: #1707 Package submission: RnaSeqSampleSize > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/slzhao/RnaSeqSampleSize > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (11:15:47): Unknown User (15:03:19): - Attachment: #1708 Package submission RnaSeqSampleSize > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/slzhao/RnaSeqSampleSize > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

2020-10-10

Unknown User (00:05:09): - Attachment: #1709 ReactomeContentService4R > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/reactome/ReactomeContentService4R > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

2020-10-11

Kozo Nishida (21:42:26): > @Kozo Nishida has joined the channel

2020-10-12

Unknown User (19:31:59): - Attachment: #1710 mutSigMapper > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/juliancandia/mutSigMapper > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

2020-10-13

Unknown User (17:55:38): Unknown User (17:55:39): Unknown User (17:55:41): Unknown User (17:55:44): Unknown User (17:55:46): Unknown User (17:55:48):

2020-10-14

Unknown User (10:27:56): - Attachment: #1711 LorisWorld > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lshep/LorisWorld.git > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (10:28:00): Unknown User (10:29:02): - Attachment: #1712 Loris World > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lshep/LorisWorld > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (10:29:06): Unknown User (10:30:24): - Attachment: #1713 LorisWorld > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lshep/LorisWorld > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (10:31:02): Unknown User (21:54:23): - Attachment: #1714 HiCDCPlus > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mervesa/HiCDCPlus > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (21:54:24): Unknown User (22:00:49): - Attachment: #1715 HiCDCPlus > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (22:00:50): Unknown User (22:01:29): - Attachment: #1716 HiCDCPlus > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mervesa/HiCDCPlus > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (22:02:26): Unknown User (22:03:07): - Attachment: #1717 HiCDCPlus > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mervesa/HiCDCPlus > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (22:07:00): Unknown User (22:08:16): - Attachment: #1718 HiCDCPlus > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mervesa/HiCDCPlus > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

2020-10-15

Unknown User (07:30:16): - Attachment: #1719 Add code of conduct > Hi, > > > > > This PR is part of the Code of Conduct dissemination activities. The BioC Code of Conduct committee thinks that it would be useful to have new contributors verify that they are aware of the code of conduct and that they will abide by it. > > > > > If you think that the wording needs to change, please feel free to edit the PR. I took the “abide by it” part from the code of conduct itself. > > > > > Best, > Leo

Unknown User (07:38:04): Unknown User (07:38:06): Unknown User (09:25:27): Unknown User (09:26:34): - Attachment: #1720 HiCDCPlus > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mervesa/HiCDCPlus > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (10:54:09): Unknown User (11:20:12): Unknown User (12:43:23): Unknown User (14:54:06): Unknown User (15:08:34): - Attachment: #1721 HiCDCPlus > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mervesa/HiCDCPlus > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (15:08:38): Unknown User (15:10:02):

2020-10-16

Unknown User (16:01:21): Unknown User (16:01:22): Unknown User (16:01:24): Unknown User (16:01:26):

2020-10-19

Unknown User (20:44:21): Unknown User (20:45:27):

2020-10-20

Unknown User (07:40:22): - Attachment: #1722 CONSTANd > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://gitlab.com/uhasselt-bioinfo/constand-r > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (07:40:24): Unknown User (08:07:09): - Attachment: #1723 CONSTANd > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/PDiracDelta/CONSTANd > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (08:07:11): Unknown User (08:11:16): - Attachment: #1724 CONSTANd > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/PDiracDelta/CONSTANd > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (17:48:49): Unknown User (17:48:51): Unknown User (17:48:53): Unknown User (17:48:55): Unknown User (17:48:56): Unknown User (17:48:57): Unknown User (17:48:58): Unknown User (17:49:00): Unknown User (17:49:01): Unknown User (17:49:03): Unknown User (17:49:04): Unknown User (17:49:06): Unknown User (17:49:08):

2020-10-21

Unknown User (14:22:57): - Attachment: #1725 preciseTADhub > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/dozmorovlab/preciseTADhub > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2020-10-22

Unknown User (15:48:02): Unknown User (15:48:04): Unknown User (15:48:05): Unknown User (15:48:06): Unknown User (15:48:08): Unknown User (15:48:10): Unknown User (15:48:12): Unknown User (15:48:13): Unknown User (15:48:14): Unknown User (15:48:16): Unknown User (15:48:17): Unknown User (15:48:19):

2020-10-23

Unknown User (13:15:59): Unknown User (13:18:35): Unknown User (13:18:36): Unknown User (13:18:38): Unknown User (13:18:40): Unknown User (13:18:41): Unknown User (13:18:43): Unknown User (13:18:44): Unknown User (13:18:46): Unknown User (14:49:20): - Attachment: #1726 TrajectoryGeometry > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/AnnaLaddach/TrajectoryGeometry > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (14:49:22):

2020-10-24

Unknown User (06:26:18): - Attachment: #1727 TrajectoryGeometry > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/AnnaLaddach/TrajectoryGeometry > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (06:26:20):

2020-10-25

Unknown User (17:29:32): - Attachment: #1728 TrajectoryGeometry > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/AnnaLaddach/TrajectoryGeometry > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2020-10-26

Unknown User (05:18:53): - Attachment: #1729 CAEN > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/zhangli1109/CAEN > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (05:18:55): Unknown User (05:35:21): - Attachment: #1730 CAEN > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/zhangli1109/CAEN > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (14:17:34): - Attachment: #1731 Submit package “mina” > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Guan06/MINA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (14:17:36): Unknown User (14:34:35): - Attachment: #1732 Submit package “mina” > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (14:34:37): Unknown User (14:36:02): - Attachment: #1733 Submit package “mina” > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Guan06/mina > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (19:37:43): - Attachment: #1734 GEOfastq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/alexvpickering/GEOfastq > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (19:37:44): Unknown User (19:41:07): - Attachment: #1735 GEOfastq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/alexvpickering/GEOfastq > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (19:41:09): Unknown User (19:43:06): - Attachment: #1736 GEOfastq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/alexvpickering/GEOfastq > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2020-10-28

Unknown User (10:17:28): - Attachment: #1737 RLassoCox > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/weiliu123/RLassoCox > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (10:17:30):

2020-10-29

Unknown User (04:52:56): - Attachment: #1738 RLassoCox > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/weiliu123/RLassoCox > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2020-10-30

Unknown User (06:16:36): - Attachment: #1739 bnem > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/MartinFXP/B-NEM > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (06:16:37): Unknown User (06:21:22): - Attachment: #1740 bnem > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/MartinFXP/bnem > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2020-11-01

Unknown User (08:09:09): - Attachment: #1741 RiboDiPA: Differential Pattern Analysis for Ribo-seq data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jipingw/RiboDiPA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (09:19:26): - Attachment: #1742 BloodGen3Module : R package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Drinchai/BloodGen3Module > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (09:19:28): Unknown User (09:25:36): - Attachment: #1743 BloodGen3Module > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Drinchai/BloodGen3Module > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (09:25:38): Unknown User (20:24:07): Unknown User (21:18:24): - Attachment: #1744 CAEN > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/zhangli1109/CAEN > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (21:18:26): Unknown User (22:23:38):

2020-11-02

Unknown User (01:40:15): - Attachment: #1745 BloodGen3Module > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Drinchai/BloodGen3Module > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (03:17:36): - Attachment: #1746 metapod > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/LTLA/metapod > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (07:38:30): - Attachment: #1747 censcyt > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/retogerber/censcyt > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (09:43:04):

2020-11-04

Unknown User (07:46:44): - Attachment: #1748 inferrnal - wrapper for Infernal RNA sequence analysis programs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/brendanf/inferrnal > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (08:33:15): - Attachment: #1749 nempi > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/cbg-ethz/nempi > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (17:22:36): - Attachment: #1750 BSgenome.Gmax.EnsemblPlants.Gmv2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/deisiany/BSgenome.Gmax.EnsemblPlants.Gmv2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (17:22:39): Unknown User (17:29:32): - Attachment: #1751 Package: BSgenome.Gmax.EnsemblPlants.Gmv2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Deisiany/BSgenome.Gmax.EnsemblPlants.Gmv2 > > > > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (17:29:34): Unknown User (17:38:48): - Attachment: #1752 Deisiany / BSgenome.Gmax.EnsemblPlants.Gmv2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Deisiany/BSgenome.Gmax.EnsemblPlants.Gmv2 > > > > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2020-11-06

Unknown User (04:08:40): - Attachment: #1753 VarCon > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/caggtaagtat/VarCon > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor [Package Submission][2] > instructions. My package is consistent with the Bioconductor > [Package Guidelines][1]. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the [support site][3] for issues that users may > have, subscribing to the [bioc-devel][4] mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the [Bioconductor code of conduct][7] and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using [Git][5] > (optionally [via GitHub][6]). > > > > > For help with submitting your package, please subscribe and post questions > to the [bioc-devel][4] mailing list.

Unknown User (04:08:43): Unknown User (04:15:41): - Attachment: #1754 VarCon (guithub now with ssh key) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/caggtaagtat/VarCon > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor [Package Submission][2] > instructions. My package is consistent with the Bioconductor > [Package Guidelines][1]. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the [support site][3] for issues that users may > have, subscribing to the [bioc-devel][4] mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the [Bioconductor code of conduct][7] and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using [Git][5] > (optionally [via GitHub][6]). > > > > > For help with submitting your package, please subscribe and post questions > to the [bioc-devel][4] mailing list.

2020-11-07

Unknown User (07:52:38): - Attachment: #1755 PFP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (07:52:39): Unknown User (07:55:10): - Attachment: #1756 PFP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/aib-group/PFP > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (07:55:12): Unknown User (08:51:47): - Attachment: #1757 PFP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/aib-group/PFP > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/

Unknown User (08:51:49): Unknown User (09:57:56):

2020-11-08

Unknown User (00:14:52): - Attachment: #1758 csawBook > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/LTLA/csawBook > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2020-11-09

Unknown User (09:33:11): - Attachment: #1759 SOMNiBUS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/kaiqiong/SOMNiBUS > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (09:33:13): Unknown User (12:58:58): - Attachment: #1760 SOMNiBUS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/kaiqiong/SOMNiBUS > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (12:59:00): Unknown User (15:24:08): - Attachment: #1761 SOMNiBUS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/kaiqiong/SOMNiBUS > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ X] The ‘devel’ branch for new packages and features. > • [ X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2020-11-10

Unknown User (09:18:32): - Attachment: #1762 PoDCall > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/HansPetterBrodal/PoDCall > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (14:04:32):

2020-11-11

Unknown User (10:47:02): - Attachment: #1763 ShinyÉPICo > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/omorante/shinyepico > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (10:47:05): Unknown User (11:02:33): - Attachment: #1764 ShinyÉPICo > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/omorante/shinyepico > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (11:04:54): Unknown User (11:04:55):

2020-11-12

Unknown User (10:16:57): - Attachment: #1765 imcdatasets > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BodenmillerGroup/imcdatasets > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2020-11-13

Unknown User (07:55:54): Unknown User (14:57:45): - Attachment: #1766 Summix > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/hendriau/Summix > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (14:57:47): Unknown User (15:00:31): - Attachment: #1767 Summix > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/hendriau/Summix > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (15:00:32): Unknown User (15:02:21): - Attachment: #1768 Summix > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/hendriau/Summix > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (15:02:22): Unknown User (15:02:40): - Attachment: #1769 Summix > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/hendriau/Summix > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (15:02:42): Unknown User (15:03:59): - Attachment: #1770 Summix > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/hendriau/Summix > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (15:04:01): Unknown User (15:05:33): - Attachment: #1771 Summix > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/hendriau/Summix > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (15:05:35): Unknown User (15:13:04): - Attachment: #1772 Summix > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/hendriau/Summix > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2020-11-16

Unknown User (11:12:02):

2020-11-17

Unknown User (10:05:03): - Attachment: #1773 MAGAR (and associated data package methQTL.data) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/MPIIComputationalEpigenetics/methQTL.data > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (10:05:04): Unknown User (10:46:06): - Attachment: #1774 MAGAR (and associated data package methQTL.data) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/MPIIComputationalEpigenetics/methQTL.data > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (10:46:09):

2020-11-18

Unknown User (07:54:36): - Attachment: #1775 SingleCellClassR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/grisslab/SingleCellClassR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (07:54:38): Unknown User (07:55:53): - Attachment: #1776 SingleCellClassR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/grisslab/SingleCellClassR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (07:55:55):

2020-11-19

Unknown User (10:34:34): - Attachment: #1777 methylclockData package - data for methylcock package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/isglobal-brge/methylclockData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X ] The ‘devel’ branch for new packages and features. > • [X ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (10:34:36): Unknown User (10:36:58): - Attachment: #1778 methylclockData - Experimenthub package related to methylclock > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/isglobal-brge/methylclockData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ X] The ‘devel’ branch for new packages and features. > • [ X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (10:37:00): Unknown User (11:33:12): - Attachment: #1779 methylclockData - Experimenthub package related to methylclock package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/isglobal-brge/methylclockData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (11:33:15): Unknown User (12:48:20): - Attachment: #1780 methylclockData - Experimenthub package related to methylclock package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/isglobal-brge/methylclockData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2020-11-20

Unknown User (02:05:07): - Attachment: #1781 https://github.com/JinmiaoChenLab/cytofkit2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (02:05:09): Unknown User (02:06:23): - Attachment: #1782 Submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/JinmiaoChenLab/cytofkit2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (02:06:25): Unknown User (02:07:45): - Attachment: #1783 Submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/JinmiaoChenLab/cytofkit2.0.0 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (02:07:47): Unknown User (02:32:35): - Attachment: #1784 SingleCellClassR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/grisslab/SingleCellClassR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (03:30:58): - Attachment: #1785 cytofkit2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/raman91/cytofkit2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (03:31:00): Unknown User (03:42:08): - Attachment: #1786 cytofkit2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/JinmiaoChenLab/cytofkit2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (03:42:10): Unknown User (07:15:48): - Attachment: #1787 MAGAR - Methylation Aware Genotype Association in R > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/MPIIComputationalEpigenetics/MAGAR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (10:31:03):

2020-11-24

Unknown User (00:44:47): - Attachment: #1788 cytofkit2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/JinmiaoChenLab/cytofkit2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (00:44:48): Unknown User (00:49:15): - Attachment: #1789 cytofkit2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (00:49:17): Unknown User (00:50:20): - Attachment: #1790 cytofkit2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/JinmiaoChenLab/cytofkit2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (00:50:22): Unknown User (00:52:33): - Attachment: #1791 cytofkit2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/JinmiaoChenLab/cytofkit2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (00:52:35): Unknown User (02:36:48): - Attachment: #1792 cytofkit2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/JinmiaoChenLab/cytofkit2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (02:56:38): - Attachment: #1793 cytofkit2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/JinmiaoChenLab/cytofkit2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (02:56:40): Unknown User (02:58:45): Unknown User (03:00:19): - Attachment: #1794 cytofkit2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/JinmiaoChenLab/cytofkit2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (03:00:21): Unknown User (03:03:46): Unknown User (13:54:33):

2020-11-26

Unknown User (02:22:06): - Attachment: #1795 SplicingFactory > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SU-CompBio/SplicingFactory > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (02:22:08): Unknown User (06:15:18):

2020-11-27

Unknown User (11:07:56): Unknown User (12:51:58): Unknown User (12:52:00): Unknown User (12:52:02): Unknown User (12:52:03): Unknown User (12:52:05): Unknown User (12:52:06): Unknown User (12:52:08):

2020-12-01

Unknown User (09:30:23): Unknown User (09:47:48): - Attachment: #1796 scTypeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/grisslab/scTypeR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > > > > Hi @mtmorgan, > > > > > As discussed this is the renamed package. > > > > > Kind regards, > Johannes

Unknown User (09:47:49): Unknown User (09:49:02): - Attachment: #1797 scTypeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/grisslab/scTypeR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (09:49:04): Unknown User (09:50:52): - Attachment: #1798 scTypeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/grisslab/scTypeR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (17:05:21): Unknown User (17:05:21): Unknown User (17:05:23): Unknown User (17:06:59):

2020-12-02

Unknown User (02:17:22): - Attachment: #1799 RoDiCE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ymatts/RoDiCE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (02:17:24): Unknown User (02:21:51): - Attachment: #1800 RoDiCE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ymatts/RoDiCE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2020-12-03

Unknown User (02:45:52): - Attachment: #1801 mumosa > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/LTLA/mumosa > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2020-12-04

Unknown User (01:14:44): - Attachment: #1802 Submission of a new package named kataegis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/flosalbizziae/kataegis > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (01:14:46): Unknown User (03:01:13): - Attachment: #1803 (inactive) Submission of a new package named kataegis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/flosalbizziae/kataegis > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2020-12-06

Unknown User (23:09:53): - Attachment: #1804 MACSr: R wrapper of MACS3 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/hubentu/MACSr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (23:09:55): Unknown User (23:13:45): - Attachment: #1805 MACSr: R wrapper of MACS3 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/hubentu/MACSr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (23:13:46):

2020-12-07

Unknown User (11:05:10): - Attachment: #1806 MACSr: R wrapper of MACS3 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/hubentu/MACSr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2020-12-12

Huipeng Li (00:39:16): > @Huipeng Li has joined the channel

Unknown User (20:26:21): - Attachment: #1807 ScaledMatrix > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/LTLA/ScaledMatrix > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (23:21:12): - Attachment: #1808 SCArray > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/zhengxwen/SCArray > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (23:21:14): Unknown User (23:23:55): - Attachment: #1809 SCArray > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/zhengxwen/SCArray > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six months, for bug fixes. > • [x] Bioconductor version control using Git (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2020-12-14

Unknown User (04:09:55): - Attachment: #1810 Louvain clustering: choosing resolution > Hi, > > > > > I am using the function igraphClustering to perform clustering using “louvain” method. I am wondering, is there a way to change the resolution? When overlaying the ADTs on the embedding, I can clearly see that one cluster is a combination of, what should be, two separate clusters. I would like to increase the resolution in order to capture those two clusters separately. TIA.

Unknown User (04:09:57): Unknown User (09:30:17): Unknown User (09:30:47): Unknown User (17:40:49): Unknown User (17:40:50): Unknown User (17:40:51): Unknown User (17:40:52):

2020-12-15

Unknown User (21:09:48): - Attachment: #1811 GeomxTools > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Nanostring-Biostats/GeomxTools > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (21:09:50): Unknown User (21:12:57): - Attachment: #1812 NanoStringNCTools > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Nanostring-Biostats/NanoStringNCTools > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (21:12:59): Unknown User (21:15:26): - Attachment: #1813 NanoStringNCTools > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Nanostring-Biostats/NanoStringNCTools > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (21:15:27): Unknown User (21:19:15): - Attachment: #1814 NanoStringNCTools > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Nanostring-Biostats/NanoStringNCTools > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (21:19:16): Unknown User (21:24:04): - Attachment: #1815 NanoStringNCTools > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Nanostring-Biostats/NanoStringNCTools > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (21:29:25): - Attachment: #1816 GeomxTools > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Nanostring-Biostats/GeomxTools > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2020-12-16

Unknown User (01:01:52): - Attachment: #1817 BumpyMatrix > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/LTLA/BumpyMatrix > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (09:51:48): - Attachment: #1818 LRcellTypeMarkers > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/marvinquiet/LRcellTypeMarkers > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (17:35:06): Unknown User (17:35:08): Unknown User (17:35:11): Unknown User (17:35:12): Unknown User (19:46:07):

2020-12-17

Unknown User (01:51:26): - Attachment: #1819 cytofkit > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/JinmiaoChenLab/cytofkit > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (01:51:28): Unknown User (01:55:23): - Attachment: #1820 cytofkit > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/JinmiaoChenLab/cytofkit > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (01:55:25): Unknown User (02:54:53): - Attachment: #1821 cytofkit > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/JinmiaoChenLab/cytofkit > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (05:32:11): - Attachment: #1822 ramr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BBCG/ramr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (05:40:48): Unknown User (06:15:04): - Attachment: #1823 TraRe > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ubioinformat/TraRe > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (10:14:32): - Attachment: #1824 SparseDOSSA2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/biobakery/SparseDOSSA2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (10:14:34): Manojkumar Selvaraju (11:13:48): > @Manojkumar Selvaraju has joined the channel

2020-12-18

Unknown User (18:23:00): - Attachment: #1825 AHPathbankDbs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/biopackathon/AHPathbankDbs > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (18:42:48): - Attachment: #1826 planet > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/wvictor14/planet > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2020-12-19

Unknown User (13:20:42): Unknown User (13:21:25): Unknown User (13:57:11): - Attachment: #1827 InteractiveComplexHeatmap > • Repository: https://github.com/jokergoo/InteractiveComplexHeatmap > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (15:41:23): - Attachment: #1828 ComPrAn > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Scavetta/ComPrAn > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2020-12-20

Unknown User (20:58:43): - Attachment: #1829 install package scuttle valid > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > > > > I have tried biocmanger，Git clone and local installation to install scuttle，but it always shows that “package ‘scuttle’ is not available (for R version 3.6.3)”, while I ensure my R.version is 3.63. This bug had troubled me for weeks. I appreciate ur help if u can help me, thank u!!!

Unknown User (20:58:44):

2020-12-21

Unknown User (14:54:01): Unknown User (14:59:41):

2020-12-22

Unknown User (05:08:56): - Attachment: #1830 conclus > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ilyessr/conclus > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2020-12-23

Unknown User (10:39:22): - Attachment: #1831 Contribute sars2pack: a compendium of accessors and utilities for COVID-19 pandemic data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/seandavi/sars2pack > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > > > > > Note to reviewers: sars2pack is not really about genomics, but about COVID-19 > data. I expect this will be of interest to the Bioconductor community, but if this > is outside the scope of Bioconductor, I can go elsewhere. > > > > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (10:39:23): Unknown User (10:43:29): - Attachment: #1832 Contribute sars2pack > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/seandavi/sars2pack > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > > > > > Note to reviewers: sars2pack is not really about genomics, but about COVID-19 > data. I expect this will be of interest to the Bioconductor community, but if this > is outside the scope of Bioconductor, I can go elsewhere. ** > > > > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (10:43:30): Unknown User (10:46:03): - Attachment: #1833 sars2pack > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/seandavi/sars2pack > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > > > > > Note to reviewers: sars2pack is not really about genomics, but about COVID-19 > data. I expect this will be of interest to the Bioconductor community, but if this > is outside the scope of Bioconductor, I can go elsewhere. ** > > > > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2020-12-26

Unknown User (05:36:04): - Attachment: #1834 ExpHunterSuite > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/seoanezonjic/ExpHunterSuite > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (05:36:05): Unknown User (05:40:13): - Attachment: #1835 ExpHunterSuite > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/seoanezonjic/ExpHunterSuite > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (10:10:34): - Attachment: #1836 PeCorA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/demar01/PeCorA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2020-12-28

Unknown User (09:55:52): - Attachment: #1837 IRISFGM > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BMEngineeR/IRISFGM > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2020-12-30

Unknown User (07:41:02): - Attachment: #1838 Travel > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Jiefei-Wang/Travel > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-01-06

Unknown User (08:12:02): Unknown User (08:20:25): - Attachment: #1839 scpdata > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/UCLouvain-CBIO/scpdata > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (10:32:38): - Attachment: #1840 Submission of factR to Bioconductor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/fursham-h/factR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (11:46:53): - Attachment: #1841 SANTA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/alexjcornish/SANTA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-01-07

Unknown User (00:10:45): - Attachment: #1842 SparseDOSSA2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/biobakery/SparseDOSSA2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (00:10:47): Unknown User (00:18:55): - Attachment: #1843 SparseDOSSA2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/biobakery/SparseDOSSA2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-01-08

Unknown User (15:02:24): - Attachment: #1844 drugseqr.data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/hms-dbmi/drugseqr.data > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-01-09

Unknown User (06:37:23): Unknown User (06:37:24): Unknown User (06:37:25): Unknown User (06:37:26):

2021-01-11

Unknown User (09:20:58): - Attachment: #1845 CelliD > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/RausellLab/CelliD > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (14:53:47):

2021-01-14

Unknown User (10:34:48): - Attachment: #1846 fobitools > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/pcastellanoescuder/fobitools > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-01-16

Unknown User (16:42:42): - Attachment: #1847 ESCO > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/JINJINT/ESCO > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (16:42:43): Unknown User (16:46:51): - Attachment: #1848 ESCO > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/JINJINT/ESCO > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-01-17

Unknown User (05:09:58): - Attachment: #1849 OSCA.intro > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/LTLA/OSCA.intro > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-01-19

Unknown User (08:52:35): - Attachment: #1850 ModCon > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/caggtaagtat/ModCon > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-01-20

Unknown User (05:24:15): - Attachment: #1851 RIC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/demar01/RIC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (23:51:03): - Attachment: #1852 OSCA.basic > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/LTLA/OSCA.basic > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-01-21

Unknown User (15:38:37):

2021-01-22

Unknown User (04:18:45): - Attachment: #1853 microbiomeDataSets > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/microbiome/microbiomeDataSets > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Annajiat Alim Rasel (15:44:56): > @Annajiat Alim Rasel has joined the channel

2021-01-23

Unknown User (14:46:50): - Attachment: #1854 drugTargetInteractions > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/girke-lab/drugTargetInteractions > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (14:46:51): Unknown User (14:48:56): - Attachment: #1855 drugTargetInteractions > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/girke-lab/drugTargetInteractions > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (14:48:57): Unknown User (14:52:13): - Attachment: #1856 drugTargetInteractions > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/girke-lab/drugTargetInteractions > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (17:33:42): Unknown User (17:33:43): Unknown User (17:33:44): Unknown User (17:33:45): Unknown User (17:33:46): Unknown User (17:33:47): Unknown User (17:33:48): Unknown User (17:33:49): Unknown User (17:33:50):

2021-01-25

Unknown User (06:24:09): - Attachment: #1857 MetaboCoreUtils > Dear Bioconductor reviewers! With this I would like to ask for inclusion of the MetaboCoreUtils package to Bioconductor. This package provides some low level core functionality for metabolomics data which can be reused across several other R/Bioconductor packages. > > > > > Please let me know if something is missing. > > > > > Thanks for your time! > cheers, jo > > > > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rformassspectrometry/MetaboCoreUtils > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (08:18:21): Unknown User (09:52:38): - Attachment: #1858 dce > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/cbg-ethz/dce > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (11:36:14): - Attachment: #1859 CTDquerier > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/isglobal-brge/CTDquerier > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (11:36:16): Unknown User (11:42:47): - Attachment: #1860 CTDquerier > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/isglobal-brge/CTDquerier > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (11:42:50): Unknown User (11:44:05): - Attachment: #1861 CTDquerier (re-submit) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/isglobal-brge/CTDquerier > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (11:44:07): Unknown User (11:44:56): - Attachment: #1862 CTDquerier_resubmit > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/isglobal-brge/CTDquerier > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (11:44:59):

2021-01-26

Unknown User (07:00:15): - Attachment: #1863 CTDquerier > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/isglobal-brge/CTDquerier > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-01-27

Unknown User (08:11:07): - Attachment: #1864 satuRn > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/statOmics/satuRn > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-01-29

Unknown User (15:28:30): - Attachment: #1865 TrajectoryUtils > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/LTLA/TrajectoryUtils > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-01-30

Unknown User (08:22:43): - Attachment: #1866 Submit R package WhisleR to Bioconductor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ZW-xjtlu/WhistleR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (08:22:45): Unknown User (08:25:37): - Attachment: #1867 Submitting package WhistleR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ZW-xjtlu/WhistleR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (08:25:38): Unknown User (08:27:15): - Attachment: #1868 Submitting Package WhistleR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ZW-xjtlu/WhistleR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (08:27:16): Unknown User (08:28:13): - Attachment: #1869 Submitting Package WhistleR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ZW-xjtlu/WhistleR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (08:28:14): Unknown User (08:30:18): - Attachment: #1870 Submitting package WhistleR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ZW-xjtlu/WhistleR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (08:30:19): Unknown User (08:32:32): - Attachment: #1871 Submitting Package WhistleR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ZW-xjtlu/WhistleR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-02-01

Unknown User (10:04:45): Unknown User (17:20:06): - Attachment: #1872 Gene Expression Variation Analysis (GEVA) > • Repository: https://github.com/sbcblab/geva > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-02-02

Unknown User (10:02:11): - Attachment: #1873 MACSr test datasets > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository:https://github.com/hubentu/MACSdata > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (14:02:02): - Attachment: #1874 autonomics > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/bhagwataditya/autonomics > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (14:04:29):

2021-02-03

Unknown User (02:05:17): - Attachment: #1875 MsFeatures > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rformassspectrometry/MsFeatures > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (02:05:19): Unknown User (02:07:06): - Attachment: #1876 MsFeatures > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rformassspectrometry/MsFeatures > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (03:34:26): - Attachment: #1877 Meaningful Immunogenetic Data at Scale > • Repository: https://github.com/Genentech/midasHLA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (03:34:28): Unknown User (03:36:22): - Attachment: #1878 Meaningful Immunogenetic Data at Scale > • Repository: https://github.com/Genentech/midasHLA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (15:45:39): Unknown User (15:45:40): Unknown User (15:45:41): Unknown User (15:45:42):

2021-02-04

Unknown User (08:40:49):

2021-02-05

Unknown User (12:25:53): - Attachment: #1879 diffUTR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ETHZ-INS/diffUTR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (18:49:06): - Attachment: #1880 PDATK: Pancreatic Ductal Adenocarcinoma Tool Kit > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (18:49:07): Unknown User (18:50:24): - Attachment: #1881 PDATK > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/bhklab/PDATK > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-02-07

Unknown User (11:58:45): - Attachment: #1882 RICdata > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/demar01/RICdata > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (11:58:47):

2021-02-08

Unknown User (08:22:18): - Attachment: #1883 interacCircos > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mrcuizhe/interacCircos > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (08:22:19): Unknown User (08:48:58): - Attachment: #1884 interacCircos > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mrcuizhe/interacCircos > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (08:49:00): Unknown User (08:51:47): - Attachment: #1885 interacCircos > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mrcuizhe/interacCircos > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-02-10

Unknown User (12:39:19):

2021-02-11

Unknown User (08:52:57): - Attachment: #1886 rawrr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/cpanse/rawrr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput mass spectrometry data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (17:40:04): Unknown User (17:40:06): Unknown User (17:40:07): Unknown User (17:40:08):

2021-02-12

Unknown User (09:17:43): Unknown User (14:08:20): - Attachment: #1887 spiky : spike-in standardization for cell-free MeDIP diagnostics and experiments > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/trichelab/spiky > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Janani Ravi (15:52:57): > @Janani Ravi has joined the channel

2021-02-15

Unknown User (00:08:33): - Attachment: #1888 OSCA.multisample > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/OSCA-source/OSCA.multisample > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (02:19:56): - Attachment: #1889 dir.expiry > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/LTLA/dir.expiry > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-02-16

Unknown User (10:35:04): - Attachment: #1890 https://github.com/suke18/FEAST > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (10:35:05): Unknown User (10:53:57): - Attachment: #1891 Submit FEAST package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/suke18/FEAST > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (10:53:59): Unknown User (15:14:57): - Attachment: #1892 DOSeq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/krishan57gupta/DOSeq > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (15:14:58): Unknown User (15:17:58): - Attachment: #1893 DOSeq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/krishan57gupta/DOSeq > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (15:18:00): Unknown User (15:29:23): - Attachment: #1894 DOSeq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/krishan57gupta/DOSeq > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > the package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-02-17

Unknown User (12:24:26): - Attachment: #1895 EWCE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/neurogenomics/ewceData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (12:24:28): Unknown User (12:30:34): - Attachment: #1896 EWCE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/neurogenomics/ewceData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (12:30:36): Unknown User (18:01:12): - Attachment: #1897 FEDUP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rosscm/FEDUP > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-02-19

Unknown User (01:42:34): - Attachment: #1898 sitadela > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/pmoulos/sitadela > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (01:42:36): Unknown User (01:45:17): - Attachment: #1899 sitadela > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/pmoulos/sitadela > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (01:45:18): Unknown User (01:54:14): - Attachment: #1900 sitadela > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/pmoulos/sitadela > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (11:24:33): - Attachment: #1901 CytoGLMM > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ChristofSeiler/CytoGLMM > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-02-22

Unknown User (04:46:01): - Attachment: #1902 multiSight > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Fjeanneret/multiSight > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (10:19:36): Unknown User (10:20:01): Unknown User (10:22:01): Unknown User (10:22:15): Unknown User (12:14:51): - Attachment: #1903 EWCE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/neurogenomics/ewceData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (12:14:53): Unknown User (12:23:53): - Attachment: #1904 EWCE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/neurogenomics/ewceData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-02-23

Unknown User (09:30:32): - Attachment: #1905 Rbec > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/PengfanZhang/Rbec > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (09:30:33): Unknown User (09:43:30): - Attachment: #1906 Rbec > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/PengfanZhang/Rbec > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (09:43:32): Unknown User (09:49:35): - Attachment: #1907 Rbec > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/PengfanZhang/Rbec > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (11:55:59): - Attachment: #1908 InterCellar > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/martaint/InterCellar > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (11:56:01): Unknown User (16:00:20): Unknown User (16:00:22): Unknown User (16:00:23): Unknown User (16:00:25):

2021-02-24

Unknown User (02:55:15): - Attachment: #1909 barcodetrackR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/dunbarlabNIH/barcodetrackR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (02:55:17): Unknown User (03:05:09): - Attachment: #1910 barcodetrackR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/dunbarlabNIH/barcodetrackR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (12:10:40): - Attachment: #1911 InterCellar > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/martaint/InterCellar > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-02-25

Unknown User (14:29:00): - Attachment: #1912 miQC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/greenelab/miQC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (14:29:02): Unknown User (15:00:27): - Attachment: #1913 miQC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/greenelab/miQC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (16:32:11): Unknown User (16:32:12): Unknown User (16:32:13):

2021-02-26

Unknown User (05:01:39): - Attachment: #1914 cyanoFilter > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/fomotis/cyanoFilter > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (05:01:40): Unknown User (06:24:20): - Attachment: #1915 cyanoFilter > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (06:24:21): Unknown User (06:32:10): - Attachment: #1916 cyanoFilter > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/fomotis/cyanoFilter > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (06:32:12): Unknown User (09:31:51): - Attachment: #1917 cyanoFilter > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/fomotis/cyanoFilter > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Krithika Bhuvanesh (11:08:04): > @Krithika Bhuvanesh has joined the channel

Krithika Bhuvanesh (11:11:23): > @Krithika Bhuvanesh has left the channel

Unknown User (11:16:19): Unknown User (14:55:37): - Attachment: #1918 BeadSorted.Saliva.EPIC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > https://github.com/bakulskilab/BeadSorted.Saliva.EPIC/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-02-27

Unknown User (14:11:56): Unknown User (15:09:18): - Attachment: #1919 methylscaper > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rhondabacher/methylscaper > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (15:09:19): Unknown User (15:11:53): - Attachment: #1920 methylscaper > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rhondabacher/methylscaper > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (15:11:54): Unknown User (15:17:54): - Attachment: #1921 methylscaper > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rhondabacher/methylscaper > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-02-28

Unknown User (19:10:50): - Attachment: #1922 genomicInstability > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/DarwinHealth/genomicInstability > • AdditionalPackage: https://github.com/DarwinHealth/HNSCgenomicInstability > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (19:10:51): Unknown User (22:13:21): - Attachment: #1923 GenomicInstability package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/DarwinHealth/HNSCgenomicInstability > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-03-01

Unknown User (03:15:52): - Attachment: #1924 XNAString: Efficient manipulation of modified oligonucleotide sequences > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/plucinskam/XNAString > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [ x The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (03:15:53): Unknown User (03:38:01): - Attachment: #1925 XNAString: Efficient manipulation of modified oligonucleotide sequences > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository:https://github.com/plucinskam/XNAString > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (09:33:55): - Attachment: #1926 hca > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Bioconductor/hca > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (11:16:14): - Attachment: #1927 PhIPData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/athchen/PhIPData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-03-02

Unknown User (05:48:01): - Attachment: #1928 Package Submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://https://github.com/ymwang233/DEpath > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (05:48:02): Unknown User (06:03:12): - Attachment: #1929 Package Submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ymwang233/DEpath > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (06:03:18): Unknown User (08:27:16): - Attachment: #1930 MsBackendMgf > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rformassspectrometry/MsBackendMgf > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-03-03

Unknown User (11:25:22): - Attachment: #1931 MsBackendMassbank > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/RforMassSpectrometry/MsBackendMassbank > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (14:11:23):

2021-03-04

Unknown User (01:35:05): - Attachment: #1932 MsBackendMassbank > • Repository: https://github.com/RforMassSpectrometry/MsBackendMassbank > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (08:16:14): Unknown User (09:24:37): - Attachment: #1933 miloR submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/MarioniLab/miloR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (09:24:39): Unknown User (09:53:33): - Attachment: #1934 miloR submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/MarioniLab/miloR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (14:43:10): - Attachment: #1935 Submit FEAST to Biocondcutor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/suke18/FEAST > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (14:43:12): Unknown User (14:47:20): - Attachment: #1936 Submit FEAST to Bioconductor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/suke18/FEAST > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (14:47:21): Unknown User (14:49:18): - Attachment: #1937 Submit FEAST to Biocondcutor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (14:49:20): Unknown User (14:50:34): - Attachment: #1938 Submit FEAST to Bioconductor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/suke18/FEAST > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (14:50:36): Unknown User (14:52:31): - Attachment: #1939 Submit FEAST to Bioconductor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/suke18/FEAST > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (14:52:34): Unknown User (15:29:23): - Attachment: #1940 Submit FEAST to Bioconductor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/suke18/FEAST > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (15:29:25): Unknown User (19:12:02): - Attachment: #1941 BioNERO > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/almeidasilvaf/BioNERO > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (22:20:37): - Attachment: #1942 Submit FEAST to Bioconductor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/suke18/FEAST > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (22:20:39): Unknown User (22:39:32): - Attachment: #1943 Submit FEAST to Bioconductor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/suke18/FEAST > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (22:39:41): - Attachment: #1944 genomicInstability > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/reef103/genomicInstability > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-03-05

Unknown User (01:46:57): - Attachment: #1945 SimBenchData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/SimBenchData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (01:46:59): Unknown User (02:49:50): - Attachment: #1946 SimBenchData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/SimBenchData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (09:43:35): - Attachment: #1947 ptairData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/camilleroquencourt/ptairData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (09:43:37): Unknown User (10:28:02): - Attachment: #1948 ptairData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/camilleroquencourt/ptairData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-03-08

Unknown User (08:03:25): Unknown User (10:47:11): Unknown User (10:47:32): Unknown User (10:48:02): Unknown User (10:49:42): - Attachment: #1949 Rbec > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/PengfanZhang/Rbec > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (10:49:43): Unknown User (10:50:03): Unknown User (14:19:09): - Attachment: #1950 CIMICE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/redsnic/CIMICE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (15:56:43): Unknown User (15:57:46): Unknown User (17:30:51): Unknown User (17:30:52): Unknown User (17:30:53): Unknown User (17:30:54): Unknown User (17:37:56): Unknown User (17:38:07): Unknown User (17:38:34):

2021-03-09

Unknown User (00:06:10): - Attachment: #1951 APAlog > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/goodarzilab/APAlog > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (00:06:12): Unknown User (02:28:15): - Attachment: #1952 APAlog > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/goodarzilab/APAlog > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (21:49:51): - Attachment: #1953 Submit FEAST to Bioconductor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/suke18/FEAST > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (21:49:53):

2021-03-10

Unknown User (10:08:14): - Attachment: #1954 GenomicSuperSignatures > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/shbrief/GenomicSuperSignature > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > > > > Additional actors: > > • @shbrief > • @lwaldron

Unknown User (10:08:16): Unknown User (16:41:59): Unknown User (22:20:45): - Attachment: #1955 condiments > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/HectorRDB/condiments/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (22:20:47): Unknown User (22:24:08): - Attachment: #1956 condiments > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/HectorRDB/condiments/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-03-11

Unknown User (15:01:38): - Attachment: #1957 EPIExPRS Package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/iloveless1/EPIExPRS > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X ] The ‘devel’ branch for new packages and features. > • [ X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-03-12

Unknown User (09:57:24): - Attachment: #1958 MatrixQCvis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tnaake/MatrixQCvis > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (09:57:26): Unknown User (10:53:16): - Attachment: #1959 MatrixQCvis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tnaake/MatrixQCvis > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (14:16:11): Unknown User (14:18:54): - Attachment: #1960 EPIExPRS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/iloveless1/EPIExPRS > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-03-14

Unknown User (03:12:51): - Attachment: #1961 submit POWSC to Bioconductor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/suke18/POWSC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (03:12:52): Unknown User (03:14:40): - Attachment: #1962 Submit POWSC to Bioconductor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/suke18/POWSC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (03:14:41): Unknown User (03:16:31): - Attachment: #1963 Submit POWSC to Bioconductor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/suke18/POWSC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (03:16:33): Unknown User (03:21:29): - Attachment: #1964 POWSC BIOCONDUCTOR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/suke18/POWSC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (23:31:57): - Attachment: #1965 lisaClust > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ellispatrick/lisaClust > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X ] The ‘devel’ branch for new packages and features. > • [X ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-03-15

Unknown User (21:14:06): - Attachment: #1966 ObMiTi > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/OmarAshkar/ObMiTi > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (21:15:07):

2021-03-16

Unknown User (00:32:50): - Attachment: #1967 treekoR - package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/adam2o1o/treekoR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (00:32:50): Unknown User (00:35:31): - Attachment: #1968 treekoR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/adam2o1o/treekoR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (00:35:33): Unknown User (00:39:30): - Attachment: #1969 treekoR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/adam2o1o/treekoR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (00:39:32): Unknown User (00:46:45): - Attachment: #1970 treekoR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/adam2o1o/treekoR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (06:02:30): Unknown User (06:06:03): - Attachment: #1971 SimBenchData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/SimBenchData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (06:06:06): Unknown User (14:48:10): Unknown User (23:37:13): - Attachment: #1972 Submission of Software epidecodeR: a functional exploration tool for epigenetic and epitranscriptomic regulation > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/kandarpRJ/epidecodeR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (23:37:15): Unknown User (23:42:37): - Attachment: #1973 epidecodeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/kandarpRJ/epidecodeR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (23:42:39): Unknown User (23:47:59): - Attachment: #1974 epidecodeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/kandarpRJ/epidecodeR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-03-17

Unknown User (07:37:53): - Attachment: #1975 cbpManager > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/arsenij-ust/cbpManager > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (10:02:31): Unknown User (10:02:33): Unknown User (10:02:35): Unknown User (10:02:36): Unknown User (10:02:37): Unknown User (10:02:38): Unknown User (10:02:39): Unknown User (13:25:17): Unknown User (13:26:28): - Attachment: #1976 MatrixQCvis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tnaake/MatrixQCvis > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (13:26:30): Unknown User (13:27:02): Unknown User (21:58:27): Unknown User (21:59:30): - Attachment: #1977 epidecodeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/kandarpRJ/epidecodeR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (21:59:32): Unknown User (22:00:15): Unknown User (23:12:33): - Attachment: #1978 Add package mirTarRnaSeq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Mercedeh66/mirTarRnaSeq.git > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (23:12:35): Unknown User (23:14:45): - Attachment: #1979 Add package mirTarRnaSeq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Mercedeh66/mirTarRnaSeq > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (23:14:47): Unknown User (23:19:54): - Attachment: #1980 Package mirTarRnaSeq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Mercedeh66/mirTarRnaSeq > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (23:19:55): Unknown User (23:22:27): - Attachment: #1981 Please add package mirTarRnaSeq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Mercedeh66/mirTarRnaSeq > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-03-18

Unknown User (02:13:06): Unknown User (10:48:31): Unknown User (22:40:53): - Attachment: #1982 geom_split_violin > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/stemangiola/ppcseq > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (22:40:54): Unknown User (22:42:34): - Attachment: #1983 Probabilistic Outlier Identification for RNA Sequencing Generalized Linear Models > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/stemangiola/ppcseq > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (22:42:35): Unknown User (22:44:58): - Attachment: #1984 ppcseq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/stemangiola/ppcseq > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (22:44:59): Unknown User (22:52:52): - Attachment: #1985 ppcseq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/stemangiola/ppcseq > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-03-19

Unknown User (00:32:52): - Attachment: #1986 ObMiTi > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/OmarAshkar/ObMiTi > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (05:46:03): - Attachment: #1987 mia > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/microbiome/mia > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (09:29:12): Unknown User (09:29:14): Unknown User (09:29:15): Unknown User (09:29:16): Unknown User (09:29:17): Unknown User (09:29:18):

2021-03-20

watanabe_st (01:57:57): > @watanabe_st has joined the channel

2021-03-21

Unknown User (04:26:47): - Attachment: #1988 DeepPINCS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/dongminjung/DeepPINCS > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-03-23

Unknown User (00:35:35): - Attachment: #1989 SURF > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/fchen365/surf > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (00:35:36): Unknown User (08:22:38): Unknown User (12:51:26): - Attachment: #1990 CNViz > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rebeccagreenblatt/CNViz > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (12:51:28): Unknown User (12:57:21): - Attachment: #1991 CNViz > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rebeccagreenblatt/CNViz > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-03-24

Unknown User (06:40:42):

2021-03-25

Unknown User (05:51:56): Unknown User (06:06:06): Unknown User (09:26:12): Unknown User (09:26:13): Unknown User (09:26:14): Catherine Ross (11:40:22): > @Catherine Ross has joined the channel

2021-03-26

Unknown User (11:19:42): - Attachment: #1992 epigraHMM > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/plbaldoni/epigraHMM > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (11:19:44): Unknown User (11:38:00): - Attachment: #1993 epigraHMM > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/plbaldoni/epigraHMM > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-03-29

Unknown User (07:20:58): - Attachment: #1994 RTIGER: A Robust HMM-based Model for genotyping-by-sequencing and Recombination Breakpoint Identification > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rfael0cm/RTIGER > Confirm the following by editing each check box to ‘[x]’ > > • [ X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (07:20:59): Unknown User (09:36:31): Unknown User (09:46:06): - Attachment: #1995 methylXprs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/iloveless1/methylXprs > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (12:45:50): - Attachment: #1996 ReactomeGraph4R > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/reactome/ReactomeGraph4R > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (17:09:16): - Attachment: #1997 memes > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/snystrom/memes > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-03-30

Unknown User (06:13:42): Unknown User (06:13:43): Unknown User (06:13:45): Unknown User (10:01:26): - Attachment: #1998 MouseThymusAgeing > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/MarioniLab/MouseThymusAgeing > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (16:17:28): - Attachment: #1999 STexampleData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lmweber/STexampleData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (16:17:29): Unknown User (16:24:05): - Attachment: #2000 STexampleData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lmweber/STexampleData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-03-31

Unknown User (00:02:03): - Attachment: #2001 GenomicSuperSignature > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/seandavi/GenomicSuperSignatures > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > > > > Additional actors: > > • @shbrief > • @lwaldron

Unknown User (00:02:05): Unknown User (00:04:14): - Attachment: #2002 GenomicSuperSignature > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/seandavi/GenomicSuperSignature > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > > > > Additional actors: > > • @shbrief > • @lwaldron

Unknown User (00:04:15): Unknown User (00:07:19): - Attachment: #2003 GenomicSuperSignature > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/seandavi/GenomicSuperSignature > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > > > > Additional actors: > > • @shbrief > • @lwaldron

Unknown User (06:48:22): - Attachment: #2004 RCSL > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/QinglinMei/RCSL > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (06:48:23): Unknown User (07:38:41): - Attachment: #2005 RCSL v1.0.0 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/QinglinMei/RCSL > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (07:38:42): Lisa Cao (12:51:44): > @Lisa Cao has joined the channel

Unknown User (19:27:08): - Attachment: #2006 NxtIRFdata > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/alexchwong/NxtIRFdata > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (19:27:09):

2021-04-01

Unknown User (20:13:13): - Attachment: #2007 AHLRBaseDbs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rikenbit/AHLRBaseDbs > • > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (20:14:08): - Attachment: #2008 AHMeSHDbs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rikenbit/AHMeSHDbs > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-04-02

Unknown User (05:49:15): - Attachment: #2009 Package scShapes > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Malindrie/scShapes > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (08:37:21): Unknown User (10:08:22): - Attachment: #2010 scShapes > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Malindrie/scShapes > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (10:08:24): Unknown User (10:27:51): - Attachment: #2011 scShapes > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Malindrie/scShapes > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-04-03

Unknown User (04:22:02): - Attachment: #2012 RCSL > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (04:22:03): Unknown User (04:22:42): - Attachment: #2013 RCSL > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/QinglinMei/RCSL > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (04:22:43): Unknown User (04:31:52): - Attachment: #2014 RCSL > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/QinglinMei/RCSL > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (07:15:20): Unknown User (07:15:21): Unknown User (10:44:13): - Attachment: #2015 RCSL > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/QinglinMei/RCSL > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (10:44:15): Unknown User (10:48:43): - Attachment: #2016 RCSL > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/QinglinMei/RCSL > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (10:48:45): Unknown User (12:31:30): - Attachment: #2017 RCSL > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/QinglinMei/RCSL > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (12:31:31):

2021-04-04

Unknown User (10:41:17): - Attachment: #2018 AHPubMedDbs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rikenbit/AHPubMedDbs > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (10:41:18): Unknown User (10:46:35): - Attachment: #2019 AHPubMedDbs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rikenbit/AHPubMedDbs > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-04-05

Unknown User (13:42:08): - Attachment: #2020 tricycle > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/hansenlab/tricycle > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (13:42:09): Unknown User (13:44:52): - Attachment: #2021 tricycle > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/hansenlab/tricycle > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (18:09:43): - Attachment: #2022 supersigs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/TomasettiLab/supersigs > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (22:28:56): - Attachment: #2023 airpart > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Wancen/airpart > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (22:28:57): Unknown User (22:32:30): - Attachment: #2024 airpart > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (22:32:31): Unknown User (22:33:38): - Attachment: #2025 airpart > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Wancen/airpart > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (22:33:39): Unknown User (22:46:29): - Attachment: #2026 airpart > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Wancen/airpart > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-04-06

Unknown User (12:15:02): - Attachment: #2027 KBoost > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > https://github.com/Luisiglm/KBoost > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (13:14:25): - Attachment: #2028 wppi > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/AnaGalhoz37/W_Annot_PPI > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (13:14:27): Unknown User (13:21:47): - Attachment: #2029 wppi > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/AnaGalhoz37/wppi > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (17:30:16): - Attachment: #2030 immunotation > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/imkeller/immunotation > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (17:30:17): Unknown User (17:36:21): - Attachment: #2031 immunotation > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/imkeller/immunotation > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (17:36:23): Unknown User (17:41:29): - Attachment: #2032 immunotation > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/imkeller/immunotation > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-04-07

Unknown User (11:34:34): - Attachment: #2033 SingleMoleculeFootprintingData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/GuidoBarzaghi/SingleMoleculeFootprintingData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (11:34:37): Unknown User (11:40:08): - Attachment: #2034 SingleMoleculeFootprintingData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/GuidoBarzaghi/SingleMoleculeFootprintingData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (19:50:55): Unknown User (19:50:56): Unknown User (19:50:57): Unknown User (19:50:58): Unknown User (19:51:00): Unknown User (19:51:01):

2021-04-08

Unknown User (02:13:16): - Attachment: #2035 dStruct > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/dataMaster-Kris/dStruct > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (19:20:17): - Attachment: #2036 granulator package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/xanibas/granulator > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-04-09

Unknown User (07:48:32): - Attachment: #2037 epialleleR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BBCG/epialleleR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (23:07:54): - Attachment: #2038 HGC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/XuegongLab/HGC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-04-10

Unknown User (18:17:31): - Attachment: #2039 SURF > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/fchen365/surf > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (18:17:33): Unknown User (18:21:59): - Attachment: #2040 SURF > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/fchen365/surf > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-04-12

Unknown User (05:30:37): - Attachment: #2041 DExMA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Juananvg/DExMAdata > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (05:30:39): Unknown User (07:16:12): - Attachment: #2042 DExMAdata > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Juananvg/DExMAdata > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (07:16:14): Unknown User (17:19:27): Unknown User (17:19:31):

2021-04-14

Unknown User (04:32:38): - Attachment: #2043 MungeSumstats > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/neurogenomics/MungeSumstats > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (04:33:00): - Attachment: #2044 TENxVisiumData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/HelenaLC/TENxVisiumData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (04:33:02): Unknown User (04:43:26): - Attachment: #2045 TENxVisiumData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/HelenaLC/TENxVisiumData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (05:34:08): - Attachment: #2046 PsiNorm submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/MatteoBlla/PsiNorm > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (17:02:59): - Attachment: #2047 msigdb > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/DavisLaboratory/msigdb > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-04-15

Unknown User (08:21:24): Unknown User (08:21:25): Unknown User (08:21:26): Unknown User (08:21:28): Unknown User (08:21:29): Unknown User (08:44:40): Unknown User (16:30:47): - Attachment: #2048 decoupleR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/saezlab/decoupleR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (23:49:02): - Attachment: #2049 FLAMES > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/OliverVoogd/FLAMES > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-04-16

Unknown User (16:42:14): - Attachment: #2050 NeuCA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/haoharryfeng/NeuCA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (16:42:15):

2021-04-17

Unknown User (01:41:11): - Attachment: #2051 NeuCA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/haoharryfeng/NeuCA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (06:10:08): - Attachment: #2052 DelayedRandomArray > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/LTLA/DelayedRandomArray > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-04-18

Unknown User (23:57:03): - Attachment: #2053 segmenter > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/MahShaaban/segmenter > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (23:57:04): Unknown User (23:59:42): - Attachment: #2054 segmenter > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/MahShaaban/segmenter > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (23:59:43):

2021-04-19

Unknown User (00:09:37): - Attachment: #2055 segmenter > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/MahShaaban/segmenter > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (00:09:38): Unknown User (00:16:45): - Attachment: #2056 segmenter > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/MahShaaban/segmenter > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (11:52:29): - Attachment: #2057 sechm (moved) > The functions included in this package were moved from the SEtools package (and will be afterwards removed from there), so as to increase granularity and reduce dependencies, as suggested by @hpages > > > > > ————————- > > > > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/plger/sechm > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-04-20

Unknown User (06:44:44): - Attachment: #2058 DExMA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Juananvg/DExMAdata > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (11:38:58): - Attachment: #2059 awst > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/drisso/awst > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (13:06:04): - Attachment: #2060 mistyR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/saezlab/mistyR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-04-21

Unknown User (08:49:00): - Attachment: #2061 MQmetrics package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BioAlvaro/MQmetrics > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (08:49:02): Unknown User (09:02:05): Unknown User (09:02:06): Unknown User (09:02:07): Unknown User (09:02:09): Unknown User (09:02:10): Unknown User (09:02:11): Unknown User (09:04:59): - Attachment: #2062 MQmetrics package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BioAlvaro/MQmetrics > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (09:09:22): Unknown User (09:28:30): - Attachment: #2063 MQmetrics > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BioAlvaro/MQmetrics > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (09:28:32): Unknown User (09:29:04): Unknown User (11:46:02): Unknown User (11:46:47): Unknown User (11:48:44): Unknown User (15:15:24): - Attachment: #2064 coMethDMR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/TransBioInfoLab/coMethDMR > > > > > Dear reviewer, I am submitting my package for the very first time. > I am a master student in the lab of @lxw391 and @gabrielodom > Thank you in advance for your feedback and your patience. > > > > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Daniela Cassol (23:46:32): > @Daniela Cassol has joined the channel

2021-04-22

Unknown User (03:48:11): - Attachment: #2065 granulator > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/xanibas/granulator > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (04:48:33): - Attachment: #2066 https://github.com/ETHZ-INS/scanMiR/ > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ETHZ-INS/scanMiR/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (04:48:34): Unknown User (04:58:18): - Attachment: #2067 https://github.com/ETHZ-INS/scanMiR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ETHZ-INS/scanMiR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (07:07:47): - Attachment: #2068 New biodb package : framework for developing database connectors. > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/pkrog/biodb > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (08:17:54): - Attachment: #2069 msqrob2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/statOmics/msqrob2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (10:17:59): Catherine Ross (14:11:23): > @Catherine Ross has left the channel

Unknown User (15:33:27): - Attachment: #2070 systemPipeTools > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/systemPipeR/systemPipeTools > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (15:33:29): Unknown User (15:39:04): - Attachment: #2071 systemPipeTools > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/systemPipeR/systemPipeTools > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (15:59:35): - Attachment: #2072 proactivWorkflow > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/GoekeLab/proactivWorkflow > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (15:59:37): Unknown User (16:56:37): - Attachment: #2073 proactivWorkflow > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/GoekeLab/proactivWorkflow > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (17:11:50): - Attachment: #2074 gwascatData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/stankiewicz565/gwascatData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (17:48:20): - Attachment: #2075 CGEN > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/nilotpalsanyal/CGEN > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (17:48:21): Unknown User (21:57:18): - Attachment: #2076 emtdata > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/DavisLaboratory/emtdata > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

2021-04-23

Unknown User (05:11:20): - Attachment: #2077 BioImageDbs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/biopackathon/BioImageDbs > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (05:11:22): Unknown User (05:21:46): - Attachment: #2078 BioImageDbs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/biopackathon/BioImageDbs > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (11:25:32): - Attachment: #2079 MSstatsLOBD > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Vitek-Lab/MSstatsLOBD > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (11:25:33): Unknown User (11:28:28): - Attachment: #2080 MSstatsLOBD > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Vitek-Lab/MSstatsLOBD > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (11:28:29): Unknown User (11:30:52): - Attachment: #2081 MSstatsLOBD > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Vitek-Lab/MSstatsLOBD > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (12:56:13): - Attachment: #2082 quantiseqr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/federicomarini/quantiseqr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (12:56:15): Unknown User (13:01:48): - Attachment: #2083 quantiseqr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/federicomarini/quantiseqr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (13:50:53): - Attachment: #2084 cosmosR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/saezlab/COSMOS > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (13:50:54): Unknown User (13:55:50): - Attachment: #2085 cosmosR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/saezlab/cosmosR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (13:55:51): Unknown User (14:04:17): - Attachment: #2086 cosmosR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/saezlab/cosmosR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (14:55:27): - Attachment: #2087 tLOH > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/USCDTG/tLOH > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (15:02:13): - Attachment: #2088 palmtree > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/HCBravoLab/palmtree > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (15:02:14): Unknown User (15:05:49): - Attachment: #2089 HubPub > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Bioconductor/HubPub > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (15:05:51): Unknown User (15:11:27): - Attachment: #2090 HubPub > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Bioconductor/HubPub > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (16:51:57): - Attachment: #2091 palmtree > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/HCBravoLab/palmtree > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (16:51:58): Unknown User (17:03:29): - Attachment: #2092 palmtree > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/HCBravoLab/palmtree > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (17:16:43): - Attachment: #2093 Dino > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/JBrownBiostat/Dino > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (18:18:46): - Attachment: #2094 AHWikipathwaysDbs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/kozo2/AHWikipathwaysDbs > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (23:38:50): Unknown User (23:38:51): Unknown User (23:38:52): Unknown User (23:38:53): Unknown User (23:38:54): Unknown User (23:38:55): Unknown User (23:38:56):

2021-04-26

Unknown User (07:00:37): - Attachment: #2095 RTDetect > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jackieduckie/RTDetect > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (07:00:38): Unknown User (07:07:20): - Attachment: #2096 RTDetect > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jackieduckie/RTDetect > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (07:07:22): Unknown User (07:51:34): - Attachment: #2097 RTDetect > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/PapenfussLab/RTDetect > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (07:51:35): Unknown User (07:53:34): - Attachment: #2098 RTDetect > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/PapenfussLab/RTDetect > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (09:56:02): - Attachment: #2099 fgga > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > https://github.com/fspetale/fgga > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ X] The ‘devel’ branch for new packages and features. > • [ X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (09:56:03):

2021-04-28

Unknown User (02:35:10): - Attachment: #2100 NUMTDetect > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/PapenfussLab/NUMTDetect > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (02:51:16): - Attachment: #2101 chromhmmData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/MahShaaban/chromhmmData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For help with submitting your package, please subscribe and post questions > to the bioc-devel mailing list. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/

Unknown User (08:47:55): Unknown User (17:06:35): Mateusz Staniak (17:52:55): > @Mateusz Staniak has joined the channel

Unknown User (19:14:58): - Attachment: #2102 fgga > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/fspetale/fgga > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X ] The ‘devel’ branch for new packages and features. > • [ X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (19:15:00): Unknown User (19:31:05): - Attachment: #2103 fgga > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/fspetale/fgga > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ X] The ‘devel’ branch for new packages and features. > • [ X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (23:24:21): - Attachment: #2104 scTreeViz > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/HCBravoLab/scTreeViz > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (23:25:20):

2021-04-29

Alan Murphy (02:13:57): > @Alan Murphy has joined the channel

Alan Murphy (02:14:26): > @Alan Murphy has left the channel

Janani Ravi (11:30:21): > @Janani Ravi has left the channel

2021-05-02

Unknown User (23:59:13): Unknown User (23:59:15): Unknown User (23:59:16): Unknown User (23:59:17): Unknown User (23:59:18): Unknown User (23:59:20): Unknown User (23:59:21):

2021-05-03

Mateusz Staniak (08:17:22): > @Mateusz Staniak has left the channel

2021-05-04

Unknown User (14:57:10): Unknown User (14:57:11): Unknown User (14:57:12): Unknown User (14:57:13): Unknown User (15:11:54): - Attachment: #2105 VeloViz > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/JEFworks-Lab/veloviz > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (15:11:56): Unknown User (23:23:32): - Attachment: #2106 BUSseq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/songfd2018/BUSseq > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

2021-05-05

Unknown User (18:27:45): - Attachment: #2107 VeloViz > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/JEFworks-Lab/veloviz > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

2021-05-06

Unknown User (02:47:24): Unknown User (02:58:20): Unknown User (10:37:26): Unknown User (10:38:04):

2021-05-07

Unknown User (02:03:40): Unknown User (02:43:04): Unknown User (06:05:04): Unknown User (06:05:12): Unknown User (06:05:13): Unknown User (06:05:14): Unknown User (06:05:16): Unknown User (06:05:17): Unknown User (06:05:18): Unknown User (06:05:19): Unknown User (06:05:20): Unknown User (06:05:22): Unknown User (06:05:23): Unknown User (06:05:24): Unknown User (06:05:25): Unknown User (06:05:26):

2021-05-10

Unknown User (10:25:41): - Attachment: #2108 CTCF > • Repository: https://github.com/mdozmorov/CTCF > > > > > This is the AnnotationHub package. The e-mail requesting further instructions and the AWS S3 access has been sent to bioc-devel@r-project.org|bioc-devel@r-project.org. > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (10:25:43): Unknown User (10:36:40): - Attachment: #2109 CTCF > Repository: https://github.com/mdozmorov/CTCF > > > > > This is the AnnotationHub package. The e-mail requesting further instructions and the AWS S3 access has been sent to bioc-devel@r-project.org|bioc-devel@r-project.org. > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

2021-05-11

Unknown User (00:56:37): Unknown User (00:56:39): Unknown User (00:56:40): Unknown User (00:56:41): Unknown User (00:56:42): Unknown User (00:56:43): Unknown User (00:56:44): Unknown User (13:20:03): Megha Lal (16:45:21): > @Megha Lal has joined the channel

Unknown User (17:07:59): Unknown User (17:08:00): Unknown User (17:08:01): Unknown User (17:08:02): Unknown User (17:08:04): Unknown User (17:08:05): Unknown User (17:08:06):

2021-05-12

Unknown User (09:04:27): Unknown User (13:45:44): Unknown User (14:25:06): Unknown User (14:55:15): Unknown User (14:55:27): Unknown User (15:14:30): Unknown User (15:19:10): Unknown User (15:41:30): Unknown User (15:41:52): Unknown User (16:09:12):

2021-05-13

Unknown User (12:55:16): Unknown User (12:55:18): Unknown User (12:55:19): Unknown User (12:55:21): Unknown User (12:55:24): Unknown User (12:55:24): Unknown User (12:55:25): Unknown User (14:19:55): Unknown User (14:19:55): Unknown User (14:19:56): Unknown User (14:19:57): Unknown User (14:42:59): Unknown User (14:43:00): Unknown User (14:43:01):

2021-05-15

Unknown User (23:56:13): - Attachment: #2110 scDetect: A rank-based ensemble learning algorithm for cell type identification of single-cell RNA sequencing in cancer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/IVDgenomicslab/scDetect/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (23:56:15):

2021-05-19

Unknown User (17:16:34): - Attachment: #2111 NanoTube submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/calebclass/NanoTube > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (17:16:35): Unknown User (21:03:20): - Attachment: #2112 NanoTube > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/calebclass/NanoTube > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

2021-05-20

Unknown User (05:01:11): - Attachment: #2113 FEVV: Functional Enrichment of Genomic Variants and Variations > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (05:01:13):

2021-05-21

Unknown User (11:02:33): Unknown User (11:03:34): Unknown User (11:34:48): Unknown User (11:36:09): Unknown User (11:36:43): Unknown User (11:44:33): Unknown User (11:45:24): Unknown User (11:47:33):

2021-05-25

Unknown User (11:23:57): - Attachment: #2114 svaNUMT > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/PapenfussLab/svaNUMT > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (11:31:26): - Attachment: #2115 svaRetro > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/PapenfussLab/svaRetro.git > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (11:31:27): Unknown User (11:33:23): - Attachment: #2116 svaRetro > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/PapenfussLab/svaRetro > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

2021-05-26

Unknown User (06:27:50): - Attachment: #2117 metapone package (software, metabolomics pathway testing) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tianwei-yu/metapone > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (06:27:52): Unknown User (06:30:23): - Attachment: #2118 metapone (software, metabolomics pathway testing) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tianwei-yu/metapone > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (06:30:24): Unknown User (06:32:11): - Attachment: #2119 metapone (software) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tianwei-yu/metapone > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (06:32:13): Unknown User (06:33:57): - Attachment: #2120 metapone (software) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tianwei-yu/metapone > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (06:33:59): Unknown User (09:11:11): Unknown User (14:32:43): - Attachment: #2121 cfDNAPro > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/hw538/cfDNAPro > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (14:32:45): Unknown User (15:42:52): - Attachment: #2122 spatzie > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jhammelman/spatzie > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (15:42:54): Unknown User (15:47:43): - Attachment: #2123 spatzie > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jhammelman/spatzie > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (16:01:09): - Attachment: #2124 cfDNAPro > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/hw538/cfDNAPro > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

2021-05-27

Unknown User (01:29:31): - Attachment: #2125 metapone > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tianwei-yu/metapone > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (01:29:33): Unknown User (03:56:08): - Attachment: #2126 m6Aboost > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ZarnackGroup/m6Aboost > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (08:33:51): - Attachment: #2127 Submit new package Magellan > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/samWieczorek/Magellan > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (08:33:53): Unknown User (08:36:38): - Attachment: #2128 New package Magellan > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/samWieczorek/Magellan > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (08:36:40): Unknown User (08:39:32): - Attachment: #2129 New package Magellan > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/samWieczorek/Magellan > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (10:13:10): - Attachment: #2130 metapone (software for metabolic pathway test) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tianwei-yu/metapone > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (10:13:11): Unknown User (10:34:38): - Attachment: #2131 metapone > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tianwei-yu/metapone > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (18:20:18): - Attachment: #2132 crisprScore > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Jfortin1/crisprScore > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (18:20:19): Unknown User (18:21:23): - Attachment: #2133 crisprScore > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Jfortin1/crisprScore > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (18:21:25):

2021-05-28

Unknown User (02:30:12): - Attachment: #2134 TxDb.Athaliana.BioMart.plantsmart51 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/athieffry/TxDb.Athaliana.BioMart.plantsmart51 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (02:30:15):

2021-06-01

Unknown User (05:49:33): - Attachment: #2135 FEVV: An R package for Functional Enrichment of Genomic Variants and Variations > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/isarnassiri/FEVV > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x]] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x]] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x]] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x]] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x]] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x]] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (05:49:35): Unknown User (05:59:09): - Attachment: #2136 FEVV: An R package for Functional Enrichment of Genomic Variants and Variations > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/isarnassiri/FEVV > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (05:59:15): Unknown User (06:06:31): - Attachment: #2137 FEVV: An R package for Functional Enrichment of Genomic Variants and Variations > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/isarnassiri/FEVV > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (17:38:19):

2021-06-04

Izaskun Mallona (08:56:45): > @Izaskun Mallona has joined the channel

2021-06-06

Unknown User (03:25:28): - Attachment: #2138 msig: An R Package for Exploring Molecular Signatures Database > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yikeshu0611/msig > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (03:25:30):

2021-06-07

Unknown User (09:44:55): - Attachment: #2139 VAExprs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/dongminjung/VAExprs > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (15:59:25):

2021-06-08

Unknown User (11:00:15): - Attachment: #2140 csdR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/AlmaasLab/csdR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (11:00:18): Unknown User (11:39:54): - Attachment: #2141 csdR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/AlmaasLab/csdR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

2021-06-09

Unknown User (17:05:28): Unknown User (17:08:20):

2021-06-10

Unknown User (01:54:19): - Attachment: #2142 DA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/xinghuq/DA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (01:54:20): Unknown User (02:09:18): - Attachment: #2143 DelayedTensor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rikenbit/DelayedTensor > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (07:53:03): - Attachment: #2144 DA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/xinghuq/DA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (07:53:05): Unknown User (07:56:12): - Attachment: #2145 DA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/xinghuq/DA/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (07:56:14): Unknown User (07:58:27): - Attachment: #2146 DA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/xinghuq/DA/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (07:58:29): Unknown User (08:19:14): - Attachment: #2147 DA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/xinghuq/DA/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (18:15:22): - Attachment: #2148 MetaGSCA > Dear Bioconductor team, > > > > > Our R package MetaGSCA got published lately in PLoS Computational Biology (10.1371/journal.pcbi.1008976). Please note that we used to submit MetaGSCA to Bioconductor in last fall (issue #1568). Now the source code has been fundamentally re-written and thus significantly optimized. It has also been shifted under a different maintainer account. So this is a brand new submission, but I’m referring to the historical submission for your reference. > > > > > Thanks, > Hui Yu > ######################################################### > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/hui-sheen/MetaGSCA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

2021-06-11

Unknown User (02:59:52): - Attachment: #2149 RPF > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ZW-xjtlu/RPF > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

2021-06-12

Unknown User (09:50:48): - Attachment: #2150 COTAN > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/seriph78/COTAN > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (09:50:49): Unknown User (09:57:02): - Attachment: #2151 COTAN > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/seriph78/COTAN > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

2021-06-16

Unknown User (09:52:35): - Attachment: #2152 denyranges > The denyranges package provides genomic coordinates of problematic genomic regions, previously known as blacklisted or exclusion regions (ENCODE data), with recommendations what to use. Additionally, it includes genome gaps, such as centromeres, telomeres, heterochromatin regions, etc. (UCSC ‘gap’ table data). All data are provided as GRanges objects. > > > > > https://github.com/mdozmorov/denyranges > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Melanie Loth (14:57:36): > @Melanie Loth has joined the channel

2021-06-17

Unknown User (12:48:11): - Attachment: #2153 crisprScoreData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Jfortin1/crisprScoreData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (12:48:12): Unknown User (13:09:08): - Attachment: #2154 crisprScoreData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Jfortin1/crisprScoreData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (13:09:09): Unknown User (13:11:53): - Attachment: #2155 crisprScoreData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Jfortin1/crisprScoreData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

2021-06-18

Unknown User (02:28:00): - Attachment: #2156 methylclock > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/isglobal-brge/methylclock/tree/RELEASE_3_13 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ X] The ‘devel’ branch for new packages and features. > • [ X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (02:28:02): Unknown User (12:31:55): - Attachment: #2157 crisprScore > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository:https://github.com/Jfortin1/crisprScore > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

2021-06-20

Unknown User (18:54:02): - Attachment: #2158 mitoClone2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/benstory/mitoClone2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

2021-06-21

Unknown User (04:53:58): - Attachment: #2159 methylclock package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/isglobal-brge/methylclock > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (07:55:10): Unknown User (08:27:03): - Attachment: #2160 spatialDmelxsim > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mikelove/spatialDmelxsim > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

2021-06-22

Unknown User (23:06:37): - Attachment: #2161 GReNA (General Regulatory Network Analysis) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jiang-junyao/GReNA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

2021-06-24

Unknown User (22:30:49): - Attachment: #2162 iPath > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/suke18/iPath > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

2021-06-25

Unknown User (16:37:16): - Attachment: #2163 BentoBoxData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/PhanstielLab/BentoBoxData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (16:37:17): Unknown User (16:40:26): - Attachment: #2164 BentoBoxData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/PhanstielLab/BentoBoxData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (16:40:27): Unknown User (16:46:51): - Attachment: #2165 BentoBoxData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/PhanstielLab/BentoBoxData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

2021-06-27

Unknown User (08:49:36): - Attachment: #2166 FindIT2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/shangguandong1996/FindIT2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

2021-06-28

Unknown User (04:47:29): - Attachment: #2167 spatialDE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/sales-lab/spatialDE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (04:47:30): Unknown User (05:42:52): - Attachment: #2168 spatialDE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/sales-lab/spatialDE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (10:37:12): - Attachment: #2169 BindingSiteFinder > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ZarnackGroup/BindingSiteFinder > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (10:37:14): Unknown User (14:31:52): - Attachment: #2170 GSE159526 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository:https://github.com/wvictor14/GSE159526 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

2021-06-29

Unknown User (03:48:40): - Attachment: #2171 traviz > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/koenvandenberge/traviz > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (03:48:41): Unknown User (03:52:14): - Attachment: #2172 traviz > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/koenvandenberge/traviz > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (03:52:16): Unknown User (04:17:28): - Attachment: #2173 traviz > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/koenvandenberge/traviz > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (08:31:57): - Attachment: #2174 BindingSiteFinder > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ZarnackGroup/BindingSiteFinder > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

2021-06-30

Unknown User (06:51:42): Unknown User (06:51:44): Unknown User (06:51:45): Unknown User (06:51:46): Unknown User (06:51:47): Unknown User (06:51:48):

2021-07-01

Unknown User (14:30:06): - Attachment: #2175 scAnnotatR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/grisslab/scAnnotatR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (14:30:08): Unknown User (16:54:23): - Attachment: #2176 scAnnotatR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/grisslab/scAnnotatR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

2021-07-06

Unknown User (07:47:15): - Attachment: #2177 cageminer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/almeidasilvaf/cageminer > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x ] The ‘devel’ branch for new packages and features. > • [ x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (09:46:59): Unknown User (17:09:33): - Attachment: #2178 rmspc > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Genometric/rmspc > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

2021-07-07

Unknown User (04:58:25): - Attachment: #2179 TabulaMurisSenisData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/fmicompbio/TabulaMurisSenisData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (07:28:02): Unknown User (13:34:39): - Attachment: #2180 BioPlex > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ccb-hms/BioPlex > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x ] The ‘devel’ branch for new packages and features. > • [ x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (16:36:42): - Attachment: #2181 enhancerHomologSearch > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jianhong/enhancerHomologSearch > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

2021-07-08

Unknown User (09:34:55): Unknown User (09:44:09): Unknown User (13:22:23):

2021-07-09

Unknown User (02:05:38): - Attachment: #2182 RegionPropertiesFeatures > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

Unknown User (02:05:39): Unknown User (02:06:56): - Attachment: #2183 RegionPropertiesFeatures > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ZW-xjtlu/RegionPropertiesFeatures > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://bioconductor.org/developers/package-guidelines/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/

2021-07-12

Unknown User (11:23:58): Unknown User (14:47:06): - Attachment: #2184 turboGliph > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/HetzDra/turboGliph > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:47:08): Unknown User (15:08:30): - Attachment: #2185 turboGliph > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/HetzDra/turboGliph > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:46:43): - Attachment: #2186 TRESS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ZhenxingGuo0015/TRESS > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:46:44): Unknown User (19:21:36):

2021-07-13

Unknown User (00:32:55): - Attachment: #2187 TRESS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ZhenxingGuo0015/TRESS > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:52:29): - Attachment: #2188 GEOexplorer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/guypwhunt/GEOexplorer > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:52:31): Unknown User (11:57:09): - Attachment: #2189 GEOexplorer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/guypwhunt/GEOexplorer > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:57:10): Unknown User (11:59:52): - Attachment: #2190 GEOexplorer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/guypwhunt/GEOexplorer > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:59:54): Unknown User (12:06:43): - Attachment: #2191 GEOexplorer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/guypwhunt/GEOexplorer > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-07-15

Unknown User (05:00:42): - Attachment: #2192 rGenomeTracks > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/OmarAshkar/rGenomeTracks/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:00:43): Unknown User (05:03:34): - Attachment: #2193 rGenomeTracks > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/OmarAshkar/rGenomeTracks/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-07-16

Unknown User (02:29:39): - Attachment: #2194 Dapar2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/samWieczorek/Dapar2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (02:29:42): Unknown User (02:32:10): - Attachment: #2195 Dapar2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/samWieczorek/Dapar2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (02:32:12): Unknown User (02:33:51): - Attachment: #2196 Dapar2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/samWieczorek/Dapar2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (02:33:52): Unknown User (02:35:49): - Attachment: #2197 Dapar2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/samWieczorek/Dapar2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (02:35:50): Unknown User (02:36:46): - Attachment: #2198 Dapar2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/samWieczorek/Dapar2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (02:36:47): Unknown User (02:47:13): - Attachment: #2199 Dapar2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/samWieczorek/Dapar2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-07-19

Unknown User (23:14:45): - Attachment: #2200 bugsigdbr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/waldronlab/bugsigdbr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-07-20

Unknown User (10:07:32): Unknown User (21:26:06): - Attachment: #2201 MAI package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/KechrisLab/MAI > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (21:26:08): Unknown User (21:31:03): - Attachment: #2202 MAI > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/KechrisLab/MAI > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (21:31:05): Unknown User (21:35:00): - Attachment: #2203 MAI > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/KechrisLab/MAI > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (23:22:12): Unknown User (23:22:13): Unknown User (23:22:14): Unknown User (23:22:17): Unknown User (23:22:19): Unknown User (23:22:20): Unknown User (23:22:21): Unknown User (23:22:22): Unknown User (23:22:23):

2021-07-21

Unknown User (12:09:41):

2021-07-22

Unknown User (14:16:32): - Attachment: #2204 netOmics > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/abodein/netOmics > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-07-26

Unknown User (08:50:30): - Attachment: #2205 ProteoDisco > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ErasmusMC-CCBC/ProteoDisco > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:50:31): Unknown User (08:56:30): - Attachment: #2206 ProteoDisco > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ErasmusMC-CCBC/ProteoDisco > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (19:13:22): - Attachment: #2207 rGenomeTracksData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/OmarAshkar/rGenomeTracksData/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (19:13:24):

2021-07-27

Unknown User (08:11:29): - Attachment: #2208 scanMiRApp > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ETHZ-INS/scanMiRApp > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming > > > > > > > > @lshep @vjcitn , following-up on the scanMiR submission, I guess it makes more sense if someone already familiar with the whole thing handles the review?

Unknown User (11:55:56): - Attachment: #2209 OptiLCMS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/xia-lab/OptiLCMS > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:55:58): Unknown User (12:24:10): - Attachment: #2210 OptiLCMS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/xia-lab/OptiLCMS > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-07-28

Unknown User (05:19:17): Unknown User (05:19:18): Unknown User (05:19:19): Unknown User (05:19:20): Unknown User (05:19:21): Unknown User (05:19:22): Unknown User (05:19:24): Unknown User (05:19:25):

2021-07-29

Unknown User (09:59:07): - Attachment: #2211 cyanoFilter > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/fomotis/cyanoFilter > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:59:09):

2021-08-01

Unknown User (06:05:00): - Attachment: #2212 Add HiC-DOC to BioCConductor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mzytnicki/HiCDOC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:56:25): - Attachment: #2213 atena > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/functionalgenomics/atena > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-08-02

Unknown User (07:29:56):

2021-08-03

Unknown User (13:32:46): - Attachment: #2214 scATAC.Explorer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/shooshtarilab/scATAC.Explorer > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:21:09): - Attachment: #2215 ADAMgui: minor fix > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jrybarczyk/ADAMgui > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:21:11): Unknown User (15:43:56): - Attachment: #2216 ADAMgui: DESCRIPTION ffix > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jrybarczyk/ADAMgui > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:43:58): Unknown User (23:03:12): Unknown User (23:04:20): - Attachment: #2217 rGenomeTracksData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/OmarAshkar/rGenomeTracksData/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-08-05

Unknown User (22:53:18): - Attachment: #2218 cpbnplot > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/noriakis/cpbnplot > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:53:20): Unknown User (22:58:58): - Attachment: #2219 cpbnplot > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/noriakis/cpbnplot > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-08-06

Lori Shepherd (17:18:01): > @Lori Shepherd has joined the channel

Lori Shepherd (17:18:38): > @Lori Shepherd has left the channel

2021-08-08

Unknown User (14:58:20): - Attachment: #2220 ggspavis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lmweber/ggspavis > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-08-09

Unknown User (04:48:31): - Attachment: #2221 TSSr-submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Linlab-slu/TSSr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor [https://bioconductor.org/developers/package-submission/](https://bioconductor.org/developers/package-submission/) > instructions. My package is consistent with the Bioconductor > [https://contributions.bioconductor.org/](https://contributions.bioconductor.org/). > > • [x] I understand Bioconductor https://bioconductor.org/developers/package-submission/#naming|[https://bioconductor.org/developers/package-submission/#naming](https://bioconductor.org/developers/package-submission/#naming) and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the [https://support.bioconductor.org](https://support.bioconductor.org) for issues that users may > have, subscribing to the [https://stat.ethz.ch/mailman/listinfo/bioc-devel](https://stat.ethz.ch/mailman/listinfo/bioc-devel) mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the [https://bioconductor.org/about/code-of-conduct/](https://bioconductor.org/about/code-of-conduct/) and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using [http://bioconductor.org/developers/how-to/git/](http://bioconductor.org/developers/how-to/git/) > (optionally [http://bioconductor.org/developers/how-to/git/sync-existing-repositories/](http://bioconductor.org/developers/how-to/git/sync-existing-repositories/)). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the [https://bioconductor.org/](https://bioconductor.org/) to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:48:32): Unknown User (05:25:28): - Attachment: #2222 TSSr-submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Linlab-slu/TSSr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor [https://bioconductor.org/developers/package-submission/](https://bioconductor.org/developers/package-submission/) > instructions. My package is consistent with the Bioconductor > [https://contributions.bioconductor.org/](https://contributions.bioconductor.org/). > > • [x] I understand Bioconductor https://bioconductor.org/developers/package-submission/#naming|[https://bioconductor.org/developers/package-submission/#naming](https://bioconductor.org/developers/package-submission/#naming) and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the [https://support.bioconductor.org](https://support.bioconductor.org) for issues that users may > have, subscribing to the [https://stat.ethz.ch/mailman/listinfo/bioc-devel](https://stat.ethz.ch/mailman/listinfo/bioc-devel) mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the [https://bioconductor.org/about/code-of-conduct/](https://bioconductor.org/about/code-of-conduct/) and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using [http://bioconductor.org/developers/how-to/git/](http://bioconductor.org/developers/how-to/git/) > (optionally [http://bioconductor.org/developers/how-to/git/sync-existing-repositories/](http://bioconductor.org/developers/how-to/git/sync-existing-repositories/)). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the [https://bioconductor.org/](https://bioconductor.org/) to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:47:15): - Attachment: #2223 orthogene > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/neurogenomics/orthogene > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:47:17): Unknown User (13:56:44): - Attachment: #2224 orthogene > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/neurogenomics/orthogene > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:56:46): Unknown User (14:46:23): - Attachment: #2225 orthogene > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/neurogenomics/orthogene > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-08-10

Unknown User (02:48:39): Unknown User (07:07:36):

2021-08-12

Unknown User (16:31:20): - Attachment: #2226 Cogito - COmpare Genomic Intervals TOol > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/annikabuerger/Cogito > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:31:22): Unknown User (16:42:12): - Attachment: #2227 Cogito - COmpare Genomic Intervals TOol > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/annikabuerger/Cogito > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-08-13

Unknown User (17:41:59): - Attachment: #2228 HPiP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mrbakhsh/HPiP > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:42:00): Unknown User (17:51:13): - Attachment: #2229 HPiP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mrbakhsh/HPiP > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:51:14): Unknown User (18:24:31): - Attachment: #2230 HPiP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mrbakhsh/HPiP > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-08-16

Unknown User (20:42:07): Unknown User (20:43:09): - Attachment: #2231 HPiP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mrbakhsh/HPiP > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:43:11): Unknown User (20:45:09): - Attachment: #2232 HPiP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mrbakhsh/HPiP > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:45:11): Unknown User (20:50:05): - Attachment: #2233 HPiP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mrbakhsh/HPiP > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:50:07): Unknown User (21:48:27):

2021-08-17

Unknown User (07:49:44): Unknown User (07:49:45): Unknown User (07:49:46): Unknown User (07:49:48): Unknown User (07:49:49): Unknown User (07:49:50): Unknown User (07:49:51): Unknown User (10:14:38): - Attachment: #2234 mbOmic > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/gongcongcong/mbOmic > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:10:30): - Attachment: #2235 netZooR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/netZoo/netZooR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:10:32): Unknown User (13:15:40): - Attachment: #2236 netZooR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/netZoo/netZooR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:15:42): Unknown User (13:18:42): - Attachment: #2237 netZooR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/netZoo/netZooR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:18:43): Unknown User (13:29:01): - Attachment: #2238 netZooR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/netZoo/netZooR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-08-18

Unknown User (10:53:52): - Attachment: #2239 drawCell > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/svalvaro/drawCell > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:53:54): Unknown User (13:29:36): - Attachment: #2240 drawCell > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/svalvaro/drawCell > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-08-19

Unknown User (08:37:16):

2021-08-20

Unknown User (12:15:40): Unknown User (14:27:09): - Attachment: #2241 plotgardenerData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/PhanstielLab/plotgardenerData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-08-23

Unknown User (08:30:29): - Attachment: #2242 SC.MEB > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Shufeyangyi2015310117/SC.MEB > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:30:32): Unknown User (09:11:00): - Attachment: #2243 SC.MEB > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:12:01): - Attachment: #2244 SC.MEB > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Shufeyangyi2015310117/SC.MEB > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:12:03): Unknown User (10:54:05): - Attachment: #2245 SC.MEB > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Shufeyangyi2015310117/SC.MEB > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:04:54): - Attachment: #2246 https://github.com/lptolik/synaptome.db > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:04:55): Unknown User (11:08:04): - Attachment: #2247 synaptome.db > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository:https://github.com/lptolik/synaptome.db > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:08:05): Unknown User (11:12:29): - Attachment: #2248 synaptome.db > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lptolik/synaptome.db > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:12:30): Unknown User (11:15:03): - Attachment: #2249 synaptome.db > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lptolik/synaptome.db > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:15:05): Unknown User (11:24:11): - Attachment: #2250 synaptome.db > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lptolik/synaptome.db > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-08-24

Unknown User (03:05:16): Unknown User (03:07:42): - Attachment: #2251 SC.MEB > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Shufeyangyi2015310117/SC.MEB > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (03:07:44): Unknown User (03:08:18): Unknown User (07:35:27): - Attachment: #2252 mosbi > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tdrose/mosbi > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:43:49): - Attachment: #2253 Submission of new package surfaltR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/EliLillyCo/surfaltR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:43:51): Unknown User (12:46:45): - Attachment: #2254 Submission of a anew package surfaltr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/EliLillyCo/surfaltr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:46:47): Unknown User (12:50:23): - Attachment: #2255 Submission of new package surfaltr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/EliLillyCo/surfaltr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:50:25): Unknown User (12:52:30): - Attachment: #2256 surfaltr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/EliLillyCo/surfaltr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:03:08):

2021-08-25

Unknown User (09:32:10): - Attachment: #2257 GeneSummary > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jokergoo/GeneSummary > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:53:59): Unknown User (12:55:25): Unknown User (12:58:03): Unknown User (12:58:28): Unknown User (13:04:17): Unknown User (13:05:03): Unknown User (13:05:22): Unknown User (13:05:29):

2021-08-26

Unknown User (09:09:03): - Attachment: #2258 transformGamPoi > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/const-ae/transformGamPoi > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:09:05): Unknown User (09:14:37): - Attachment: #2259 Metapone (software package for weighted pathway testing for untargeted metabolomics data) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tianwei-yu/metapone > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:14:39): Unknown User (09:21:05): - Attachment: #2260 Metapone revised. Sorry for missing the previous deadline. Can you re-open the submission? > Thank you for your submission. please find the initial review below: > > > > > General > > > > > Currently the package does not show much interoperability for Bioconductor classes and structure nor does it use existing > Bioconductor functionality for parallelization (BiocParallel). > > > > > Build Report > > > > > • [x] Please fix all NOTES of the build report > > > > > DESCRIPTION > > > > > • [x] See notes from build report > > > > > data/man > > > > > • [x] There is no information on how the neg or pos data was generated? And it is not well documented in the vignette either; if they are outcomes of data it should be documented, if they are simulated data then how it was generated selected should be made more clear. > • [x] There should be more explanation on how all the data was generated. The the data man pages are minimal. It would be helpful to not only describe the structure of the data object but any filters, specifications, etc.. There is no real detail on the source information provided. What it is? How its used? > > > > > inst > > > > > • [x] All vignettes should be in the vignette directory and not inst/doc/. Please git remove. > > > > > vignette > > > > > • [x] Based on the README and vignette which seem the same, you should create accessor methods for different parts of your results object rather than using the @ directly. > > • [x] The vignette is very superficial. Please explain more about what your package accomplishes and how it is different from other applications. > > • [x] Again pos and neg are not well defined or clear if it is outcome of real experiments or if they are simulated. > > • [x] The table at the end of the vignette is too big and does not display properly. Consider truncating and formatting. > > • [x] What are SMPDB and mummichog. There are no references or explanation. > > • [x] It would be useful to show how other existing Bioconductor packages would fit into using your package. > > > > > > R/man > > > > > • [x] Generally we like to see formalized S4 classes rather than S3 classes. > > • [x] Use BiocParallel instead of generic parallelization. > > • [x] Are there any exisiting Bioconductor classes and structures that could be utilized? > > > > > > Unfortunately no. > > > > > Please address the above issues. When ready please comment back here with explanations and how the above concerns have been addressed and kick off a version bump in the description to trigger a new build. Thank you. > > > > > Originally posted by @lshep in https://github.com/Bioconductor/Contributions/issues/2131#issuecomment-875555834

Unknown User (09:21:06): Unknown User (09:24:03): - Attachment: #2261 Metapone (previously closed submission because I was late in addressing the issues). Can you re-open the submission? > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tianwei-yu/metapone > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:24:05): Unknown User (09:24:18): - Attachment: #2262 transformGamPoi > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/const-ae/transformGamPoi > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:13:30): Unknown User (11:13:59): Unknown User (11:14:00): Unknown User (11:14:01): Unknown User (11:14:02): Unknown User (13:07:57): - Attachment: #2263 tanggle > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/KlausVigo/tanggle > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-08-29

Unknown User (01:18:08): - Attachment: #2264 scReClassify > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/scReClassify > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (01:18:10): Unknown User (01:22:06): - Attachment: #2265 scReClassify > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/scReClassify > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (01:22:08): Unknown User (01:50:17): - Attachment: #2266 scReClassify > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/scReClassify > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-09-01

Unknown User (05:36:13): Unknown User (05:36:26): Unknown User (06:08:45): - Attachment: #2267 tripr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BiodataAnalysisGroup/tripr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:06:22): - Attachment: #2268 microbiomeMarker > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yiluheihei/microbiomeMarker > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:28:24): Unknown User (14:39:25): - Attachment: #2269 excluderanges > https://github.com/mdozmorov/excluderanges > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-09-03

Unknown User (11:08:30): Unknown User (11:08:31): Unknown User (11:08:32): Unknown User (11:08:33): Unknown User (13:25:41): - Attachment: #2270 ODER > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/eolagbaju/ODER > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-09-04

Unknown User (22:04:38): - Attachment: #2271 Cepo > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/PYangLab/Cepo > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:04:40):

2021-09-06

Unknown User (20:30:59): - Attachment: #2272 scatterHatch > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/FertigLab/scatterHatch > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-09-07

Unknown User (14:36:17):

2021-09-09

Unknown User (22:27:01): - Attachment: #2273 org.Pelliottii.eg.db > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BioDING2021/org.Pelliottii.eg.db > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:27:02):

2021-09-10

Unknown User (08:35:57): Unknown User (09:51:56): - Attachment: #2274 Submission of new package, seqpac: for small RNA analysis: from fastq (trimming included) to interpretation > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Danis102/seqpac > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > > > > > Submitter: There are very few specific warnings/errors: for example that we don’t > have enough run-able examples, using too much of \donttest{}. But since our package > depend on user provided references for best function, we cannot provide good examples with fully > functional code all the time. We have, however, tried to provide as many self-sustained examples as possible. > We hope that this is something reviewers may test and comment on during the review process, but we > have tried to fix all R CMD checks and BioChecks as far as we can without disturbing package examples and fuctions. > > > > > > > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:51:59): Unknown User (10:03:24): - Attachment: #2275 Submission of new package, seqpac: for small RNA analysis: from fastq (trimming included) to interpretation > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Danis102/seqpac > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > > > > > Submitter: There are very few specific warnings/errors: for example that we don’t > have enough run-able examples, using too much of \donttest{}. But since our package > depend on user provided references for best function, we cannot provide good examples with fully > functional code all the time. We have, however, tried to provide as many self-sustained examples as possible. > We hope that this is something reviewers may test and comment on during the review process, but we > have tried to fix all R CMD checks and BioChecks as far as we can without disturbing package examples and fuctions > > > > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:50:19): Unknown User (11:50:20): Unknown User (11:50:22): Unknown User (12:29:13): - Attachment: #2276 monaLisa: MOtif aNAlysis with Lisa > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/fmicompbio/monaLisa > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-09-13

Unknown User (22:08:14): - Attachment: #2277 New package submission: Benchmark scRNA-seq Data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/gcgreenberg/benchmark.data.scRNAseq/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:08:15): Unknown User (22:12:30): - Attachment: #2278 New package submission: Benchmark scRNAseq Data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/gcgreenberg/benchmark.data.scRNAseq/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:12:32): Unknown User (22:49:36): - Attachment: #2279 New package submission: Benchmark scRNAseq Data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/gcgreenberg/benchmark.data.scRNAseq/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-09-14

Unknown User (04:55:26): - Attachment: #2280 imcRtools > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BodenmillerGroup/imcRtools > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-09-15

Unknown User (06:14:30): - Attachment: #2281 New package Magellan > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/samWieczorek/Magellan > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (06:14:32): Unknown User (06:44:44): Unknown User (08:44:31): - Attachment: #2282 Synaptome.data package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lptolik/synaptome.data > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:47:00): - Attachment: #2283 biodbChebi (an extension package of biodb package) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/pkrog/biodbChebi > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:54:26): - Attachment: #2284 Cepo > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/PYangLab/Cepo > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:25:12): - Attachment: #2285 biodbUniprot (biodb extension package) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/pkrog/biodbUniprot > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:02:19): - Attachment: #2286 biodbHmdb (biodb extension package) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/pkrog/biodbHmdb > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:42:36): - Attachment: #2287 biodbLipidmaps (biodb extension package) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/pkrog/biodbLipidmaps > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:11:27): - Attachment: #2288 biodbKegg (biodb extension package) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/pkrog/biodbKegg > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (23:12:27): - Attachment: #2289 curatedTBData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/compbiomed/curatedTBData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (23:12:29): Unknown User (23:25:01): - Attachment: #2290 curatedTBData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/compbiomed/curatedTBData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (23:25:03):

2021-09-16

Unknown User (10:17:11): Unknown User (15:08:53): - Attachment: #2291 curatedTBData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/compbiomed/curatedTBData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:08:55): Unknown User (15:18:50): - Attachment: #2292 curatedTBData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/compbiomed/curatedTBData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:59:17): - Attachment: #2293 NxtIRF data package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/alexchwong/NxtIRFdata > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-09-17

Unknown User (08:49:08): - Attachment: #2294 epimutacions > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/isglobal-brge/epimutacions > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:49:29): - Attachment: #2295 sciCNV > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/alimahdipour/sciCNV > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:04:50): - Attachment: #2296 CDI > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://gitlab.oit.duke.edu/jichunxie/xie-lab-software_cdi > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:04:51): Unknown User (17:40:54): - Attachment: #2297 CDI > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jichunxie/CDI > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-09-19

Unknown User (04:13:24): - Attachment: #2298 sccomp > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/stemangiola/sccomp > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:13:26): Unknown User (04:19:26): - Attachment: #2299 sccomp > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/stemangiola/sccomp > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:29:45): - Attachment: #2300 scDDboost > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/wiscstatman/scDDboost > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:29:47): Unknown User (12:32:22): - Attachment: #2301 scDDboost > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/wiscstatman/scDDboost > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:32:24): Unknown User (12:33:58): - Attachment: #2302 scDDboost > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/wiscstatman/scDDboost > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:33:59): Unknown User (12:34:50): - Attachment: #2303 scDDboost > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/wiscstatman/scDDboost > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:34:51): Unknown User (23:30:59): Unknown User (23:31:11):

2021-09-20

Unknown User (01:03:11): - Attachment: #2304 GenProSeq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/dongminjung/GenProSeq > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (03:11:09): - Attachment: #2305 synapsis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mcneilllucy/synapsis > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (03:11:11): Unknown User (03:13:49): - Attachment: #2306 synapsis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mcneilllucy > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:28:54): Unknown User (22:30:17): - Attachment: #2307 synapsis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mcneilllucy/synapsis > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:30:18): Unknown User (22:33:54): - Attachment: #2308 synapsis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://https://github.com/mcneilllucy/synapsis > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:33:56): Unknown User (22:37:59): - Attachment: #2309 synapsis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://https://github.com/mcneilllucy/synapsis > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-09-21

Unknown User (05:12:11): - Attachment: #2310 lineagespot > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BiodataAnalysisGroup/lineagespot > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:12:12): Unknown User (05:33:33): - Attachment: #2311 lineagespot > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BiodataAnalysisGroup/lineagespot > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [Χ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [Χ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [Χ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [Χ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [Χ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [Χ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [Χ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [Χ] The ‘devel’ branch for new packages and features. > • [Χ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [Χ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:33:34): Unknown User (05:50:51): - Attachment: #2312 lineagespot > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BiodataAnalysisGroup/lineagespot > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:50:53): Unknown User (05:54:25): - Attachment: #2313 lineagespot > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BiodataAnalysisGroup/lineagespot > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:54:26): Unknown User (05:57:33): - Attachment: #2314 lineagespot > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BiodataAnalysisGroup/lineagespot > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:29:24): - Attachment: #2315 pengls > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/sthawinke/pengls > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:29:26): Unknown User (10:31:53): - Attachment: #2316 pengls > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/sthawinke/pengls > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-09-22

Unknown User (03:15:46): - Attachment: #2317 ggmsa > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/YuLab-SMU/ggmsa > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (03:15:47): Unknown User (03:27:43): - Attachment: #2318 ggmsa > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/YuLab-SMU/ggmsa > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (06:55:26): - Attachment: #2319 MicrobiomeProfiler > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (06:55:27): Unknown User (06:57:08): - Attachment: #2320 MicrobiomeProfiler > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/YuLab-SMU/MicrobiomeProfiler > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:31:09): Unknown User (14:43:17): Unknown User (14:43:18): Unknown User (14:43:19): Unknown User (14:43:20): Unknown User (14:43:22): Unknown User (17:01:04): Unknown User (18:46:18): - Attachment: #2321 sciCNV > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:50:51): Unknown User (18:50:58):

2021-09-23

Unknown User (09:08:18): - Attachment: #2322 CellBarcode > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/wenjie1991/CellBarocde/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:37:08): - Attachment: #2323 pairkat > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Ghoshlab/pairkat > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:37:10): Unknown User (13:51:42): - Attachment: #2324 pairkat > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > Repository: https://github.com/Ghoshlab/pairkat > Confirm the following by editing each check box to ‘[x]’ > > > > > [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > > > > [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > > > > [ x] I understand Bioconductor Package Naming Policy and acknowledge > Bioconductor may retain use of package name. > > > > > [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > > > > [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > > > > [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > [ x] The ‘devel’ branch for new packages and features. > [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > [ x] Bioconductor version control using Git > (optionally via GitHub). > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up.

Unknown User (18:20:29): Unknown User (18:20:37): Unknown User (18:22:33): Unknown User (18:23:01): - Attachment: #2325 CellBarocde > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/wenjie1991/CellBarocde > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:23:03): Unknown User (18:25:07): - Attachment: #2326 CellBarcode > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/wenjie1991/CellBarcode > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-09-24

Unknown User (06:46:22): - Attachment: #2327 RiboCrypt > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Miswi/RiboCrypt > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (06:46:23): Unknown User (07:12:54): - Attachment: #2328 RiboCrypt > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/m-swirski/RiboCrypt > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:52:33): - Attachment: #2329 TargetDecoy > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/statOmics/TargetDecoy > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:52:34): Unknown User (08:57:40): - Attachment: #2330 TargetDecoy > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/statOmics/TargetDecoy > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:57:42): Unknown User (09:04:48): - Attachment: #2331 TargetDecoy > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/statOmics/TargetDecoy > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-09-25

Unknown User (18:46:30): - Attachment: #2332 deconvR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BIMSBbioinfo/deconvR > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-09-26

Unknown User (07:25:43): - Attachment: #2333 comapr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ruqianl/comapr > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:25:45): Unknown User (07:35:07): - Attachment: #2334 comapr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:35:08): Unknown User (07:36:18): - Attachment: #2335 comapr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ruqianl/comapr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:16:57): - Attachment: #2336 resubmission of TSSr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:16:59): Unknown User (11:18:40): - Attachment: #2337 TSSr submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Linlab-slu/TSSr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:18:42):

2021-09-27

Unknown User (10:10:27): - Attachment: #2338 ggmanh > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/leejs-abv/ggmanh > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:18:42): - Attachment: #2339 MsBackendRawFileReader Public > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/fgcz/MsBackendRawFileReader > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [ X The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:16:48): Unknown User (18:33:42): - Attachment: #2340 sciCNV > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/alimahdipour/sciCNV > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming > > sciCNV-master (2).zip

Unknown User (18:33:44): Unknown User (18:37:39): - Attachment: #2341 sciCNV > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/alimahdipour/sciCNV > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:37:41):

2021-09-29

Unknown User (05:57:20): - Attachment: #2342 sparrow > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lianos/sparrow > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (06:32:24): - Attachment: #2343 SCEnt > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/hwarden162/SCEnt > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (06:32:26): Unknown User (10:23:55): - Attachment: #2344 benchdamic > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mcalgaro93/benchdamic > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:55:42): - Attachment: #2345 BOBaFIT package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/bioinformatic-seragnoli/BOBaFIT > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:10:38): - Attachment: #2346 miaSim > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/microbiome/miaSim > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:23:09): - Attachment: #2347 scDDboost > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/wiscstatman/scDDboost > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:23:11): Unknown User (15:29:26): - Attachment: #2348 scDDboost > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/wiscstatman/scDDboost > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:29:27): Unknown User (15:41:26): - Attachment: #2349 scDDboost > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/wiscstatman/scDDboost > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:16:18): - Attachment: #2350 RLHub > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Bishop-Laboratory/RLHub > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-09-30

Unknown User (04:08:53): - Attachment: #2351 cliProfiler > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Codezy99/cliProfiler > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:44:45): - Attachment: #2352 nullrangesData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/nullranges/nullrangesData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:32:52): - Attachment: #2353 CNVMetrics > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/KrasnitzLab/CNVMetrics > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:32:54): Unknown User (11:42:19): - Attachment: #2354 CNVMetrics > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/KrasnitzLab/CNVMetrics > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:08:29): - Attachment: #2355 stankiewicz565 / gwascatData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:08:30): Unknown User (12:45:18): - Attachment: #2356 stankiewicz565/ontoProcData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/stankiewicz565/ontoProcData > > > > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:14:33): - Attachment: #2357 GeoMxWorkflows > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Nanostring-Biostats/GeoMxWorkflows > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:10:51): - Attachment: #2358 MSstatsLiP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Vitek-Lab/MSstatsLiP > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:10:53): Unknown User (16:13:34): - Attachment: #2359 MSstatsLiP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Vitek-Lab/MSstatsLiP > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:04:09): - Attachment: #2360 CyTOFpower > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/FerreiraAM/CyTOFpower > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-10-01

Unknown User (03:14:42): - Attachment: #2361 txcutr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mfansler/txcutr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:22:37): - Attachment: #2362 epistack > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/GenEpi-GenPhySE/epistack > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Michael Love (08:50:03): > @Michael Love has joined the channel

Michael Love (08:51:10) (in thread): > I submitted this yesterday but it didn’t get a label, maybe I made a typo but I can’t spot it… - File (PNG): Screen Shot 2021-10-01 at 8.50.51 AM.png

Unknown User (09:30:17): - Attachment: #2363 tuberculosis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/schifferl/tuberculosis > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming > > > > > ————————- > > > > > > Adding a note here, there are a number of places where code is commented out because the requisite ExperimentHub records have not been inserted into the production database yet. I have uploaded to S3 and sent my metadata.csv file, but from conversation with Marcel I understand no one is available to finalize the process until at least Monday. I am submitting the package here to meet the deadline for the release and will make a few changes when the ExperimentHub resources become available. The package will work much like curatedMetagenomicData does.

Unknown User (09:30:19): Unknown User (09:38:22): - Attachment: #2364 tuberculosis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/schifferl/tuberculosis > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming > > > > > ————————- > > > > > > Adding a note here, there are a number of places where code is commented out because the requisite ExperimentHub records have not been inserted into the production database yet. I have uploaded to S3 and sent my metadata.csv file, but from conversation with Marcel I understand no one is available to finalize the process until at least Monday. I am submitting the package here to meet the deadline for the release and will make a few changes when the ExperimentHub resources become available. The package will work much like curatedMetagenomicData does.

Unknown User (09:38:23): Unknown User (09:39:45): - Attachment: #2365 tuberculosis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/schifferl/tuberculosis > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming > > > > > ————————- > > > > > > Adding a note here, there are a number of places where code is commented out because the requisite ExperimentHub records have not been inserted into the production database yet. I have uploaded to S3 and sent my metadata.csv file, but from conversation with Marcel I understand no one is available to finalize the process until at least Monday. I am submitting the package here to meet the deadline for the release and will make a few changes when the ExperimentHub resources become available. The package will work much like curatedMetagenomicData does.

Unknown User (09:39:46): Unknown User (09:55:55): - Attachment: #2366 tuberculosis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/schifferl/tuberculosis > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming > > > > > ————————- > > > > > > Adding a note here, there are a number of places where code is commented out because the requisite ExperimentHub records have not been inserted into the production database yet. I have uploaded to S3 and sent my metadata.csv file, but from conversation with Marcel I understand no one is available to finalize the process until at least Monday. I am submitting the package here to meet the deadline for the release and will make a few changes when the ExperimentHub resources become available. The package will work much like curatedMetagenomicData does.

Unknown User (09:55:57): Unknown User (09:57:16): - Attachment: #2367 tuberculosis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/schifferl/tuberculosis > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming > > > > > ————————- > > > > > > Adding a note here, there are a number of places where code is commented out because the requisite ExperimentHub records have not been inserted into the production database yet. I have uploaded to S3 and sent my metadata.csv file, but from conversation with Marcel I understand no one is available to finalize the process until at least Monday. I am submitting the package here to meet the deadline for the release and will make a few changes when the ExperimentHub resources become available. The package will work much like curatedMetagenomicData does.

Unknown User (09:57:18): Unknown User (09:59:54): - Attachment: #2368 tuberculosis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/schifferl/tuberculosis > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming > > > > > ————————- > > > > > > Adding a note here, there are a number of places where code is commented out because the requisite ExperimentHub records have not been inserted into the production database yet. I have uploaded to S3 and sent my metadata.csv file, but from conversation with Marcel I understand no one is available to finalize the process until at least Monday. I am submitting the package here to meet the deadline for the release and will make a few changes when the ExperimentHub resources become available. The package will work much like curatedMetagenomicData does.

Unknown User (09:59:55): Unknown User (10:09:37): - Attachment: #2369 tuberculosis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/schifferl/tuberculosis > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming > > > > > ————————- > > > > > > Adding a note here, there are a number of places where code is commented out because the requisite ExperimentHub records have not been inserted into the production database yet. I have uploaded to S3 and sent my metadata.csv file, but from conversation with Marcel I understand no one is available to finalize the process until at least Monday. I am submitting the package here to meet the deadline for the release and will make a few changes when the ExperimentHub resources become available. The package will work much like curatedMetagenomicData does.

Unknown User (10:09:38): Unknown User (10:41:14): - Attachment: #2370 easierData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/olapuentesantana/easierData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:41:16): Unknown User (10:50:03): - Attachment: #2371 easierData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/olapuentesantana/easierData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:50:05): Unknown User (11:17:41): - Attachment: #2372 easierData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/olapuentesantana/easierData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:17:43): Unknown User (11:22:06): - Attachment: #2373 easierData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/olapuentesantana/easierData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:22:07): Unknown User (11:38:45): - Attachment: #2374 easierData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/olapuentesantana/easierData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:21:42): - Attachment: #2375 tuberculosis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/schifferl/tuberculosis > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming > > > > > ————————- > > > > > > Adding a note here, there are a number of places where code is commented out because the requisite ExperimentHub records have not been inserted into the production database yet. I have uploaded to S3 and sent my metadata.csv file, but from conversation with Marcel I understand no one is available to finalize the process until at least Monday. I am submitting the package here to meet the deadline for the release and will make a few changes when the ExperimentHub resources become available. The package will work much like curatedMetagenomicData does.

Unknown User (15:14:05): - Attachment: #2376 cytoKernel > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Ghoshlab/cytoKernel > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:37:22): - Attachment: #2377 GeoDiff > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Nanostring-Biostats/GeoDiff > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:46:23): Unknown User (20:46:24): Unknown User (20:46:25): Unknown User (20:46:26): Unknown User (20:46:28): Unknown User (20:46:29): Unknown User (22:50:09): - Attachment: #2378 Yeskit > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ncrna/Yeskit > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-10-04

Unknown User (09:46:54): - Attachment: #2379 GBScleanR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tomoyukif/GBScleanR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [ x The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:46:56): Unknown User (09:57:21): - Attachment: #2380 GBScleanR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tomoyukif/GBScleanR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-10-05

Unknown User (04:39:57): Unknown User (12:27:16): Unknown User (12:37:04): Unknown User (19:16:05):

2021-10-06

Unknown User (18:05:03): - Attachment: #2381 sciCNV > Update the following URL to point to the GitHub repository of > sciCNV > > > > > • Repository: https://github.com/alimahdipour/sciCNV > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:05:06):

2021-10-07

Unknown User (10:56:15): Unknown User (12:28:21): - Attachment: #2382 sciCNV > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/alimahdipour/sciCNV > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:28:23): Unknown User (12:30:21): - Attachment: #2383 sciCNV > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/alimahdipour/sciCNV > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-10-08

Unknown User (03:52:55): - Attachment: #2384 rprimer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/sofpn/rprimer > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:46:36): - Attachment: #2385 package submission distSTRING > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/kullrich/distSTRING > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:07:44): Unknown User (09:07:45): Unknown User (09:07:46): Unknown User (09:07:48): Unknown User (09:07:49): Unknown User (09:07:50): Unknown User (09:07:52): Unknown User (09:07:53): Unknown User (09:07:54):

2021-10-12

Unknown User (03:51:20): Unknown User (06:07:42): Unknown User (13:54:06): Unknown User (13:54:07): Unknown User (13:54:09): Unknown User (13:54:10): Unknown User (13:54:11): Unknown User (13:54:12): Unknown User (13:54:13): Unknown User (13:54:14):

2021-10-14

Unknown User (09:45:32): Unknown User (09:45:33): Unknown User (09:45:35): Unknown User (09:45:36):

2021-10-15

Unknown User (04:40:04): Unknown User (04:40:16): Unknown User (09:58:14):

2021-10-16

Unknown User (01:47:58): - Attachment: #2386 best.friends > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/favorov/best-friends/R/best.friends > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (01:47:59): Unknown User (02:31:00): - Attachment: #2387 best.friends > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/favorov/best.friends > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-10-17

Unknown User (22:26:50): - Attachment: #2388 LINEAGE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/songjiajia2018/LINEAGE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:26:52):

2021-10-19

Unknown User (00:54:44): - Attachment: #2389 octad.db > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (00:54:45): Unknown User (01:29:16): - Attachment: #2390 octad.db > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Bin-Chen-Lab/OCTAD.db > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (01:29:18): Unknown User (01:30:19): - Attachment: #2391 octad.db > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Bin-Chen-Lab/octad.db > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (02:45:59): - Attachment: #2392 LINEAGE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/songjiajia2018/LINEAGE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (02:46:00): Unknown User (03:22:29): - Attachment: #2393 LINEAGE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/songjiajia2018/LINEAGE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:05:12): Unknown User (11:05:12): Unknown User (11:05:14): Unknown User (11:05:15): Unknown User (11:05:17): Unknown User (11:05:19): Unknown User (11:05:20): Unknown User (11:05:22): Unknown User (11:05:23): Unknown User (11:05:25): Unknown User (11:05:26): Unknown User (11:05:28): Unknown User (11:05:30): Unknown User (11:05:32): Unknown User (11:05:34): Unknown User (13:13:47):

2021-10-20

Unknown User (07:11:58): Unknown User (07:21:49): Unknown User (07:22:26): Unknown User (12:22:35): Unknown User (12:22:36): Unknown User (12:22:37): Unknown User (12:22:39): Unknown User (16:13:07):

2021-10-21

Unknown User (03:06:24): - Attachment: #2394 https://github.com/da-bar/JASPAR2022 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (03:06:25): Unknown User (03:08:09): - Attachment: #2395 JASPAR2022 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/da-bar/JASPAR2022 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (03:08:11):

2021-10-22

Unknown User (13:16:33): Unknown User (13:16:34): Unknown User (13:16:35): Unknown User (13:16:37): Unknown User (13:16:38): Unknown User (13:16:39): Unknown User (13:16:42): Unknown User (13:16:44):

2021-10-25

Unknown User (14:51:51): Unknown User (15:03:17): Unknown User (20:28:57): - Attachment: #2396 crisprBase > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Jfortin1/crisprBase > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:28:57): Unknown User (20:30:29): - Attachment: #2397 crisprBase > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Jfortin1/crisprBase > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:30:31): Unknown User (20:43:22): - Attachment: #2398 crisprBase > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Jfortin1/crisprBase > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-10-26

Unknown User (10:39:19): - Attachment: #2399 RCX > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/frankkramer-lab/RCX > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-10-27

Unknown User (00:38:19): - Attachment: #2400 Netie > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tianshilu/Netie > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming > > netie_1.0.tar.gz

Unknown User (00:38:22): Unknown User (00:41:29): - Attachment: #2401 Netie > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tianshilu/Netie > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (00:41:31): Unknown User (00:46:06): - Attachment: #2402 Netie > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tianshilu/Netie > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor Package Naming Policy and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/Netie

Unknown User (00:46:08): Unknown User (00:48:47): - Attachment: #2403 Netie > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tianshilu/Netie > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor Package Naming Policy and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/Netie

Unknown User (00:48:48): Unknown User (00:50:43): - Attachment: #2404 netie > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tianshilu/netie > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor Package Naming Policy and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/netie

Unknown User (00:50:46): Unknown User (00:52:35): - Attachment: #2405 netie > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tianshilu/netie > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor Package Naming Policy and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/netie

Unknown User (00:52:36): Unknown User (11:38:38): - Attachment: #2406 New package hermes submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/insightsengineering/hermes > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:38:40): Unknown User (11:38:42): Unknown User (11:48:04): - Attachment: #2407 sciCNV > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/alimahdipour/sciCNV > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:48:06): Unknown User (11:51:48): - Attachment: #2408 sciCNV > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/alimahdipour/sciCNV > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:51:49): Unknown User (11:52:31): Unknown User (12:03:12): - Attachment: #2409 netie > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tianshilu/netie > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor Package Naming Policy and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/netie

Unknown User (12:03:14): Unknown User (12:05:23): - Attachment: #2410 netie > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tianshilu/netie > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor Package Naming Policy and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/netie

Unknown User (12:05:26): Unknown User (12:09:31): - Attachment: #2411 netie > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tianshilu/netie > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor Package Naming Policy and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/netie

Unknown User (12:09:33):

2021-10-29

Unknown User (02:55:58): - Attachment: #2412 New package hermes > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/insightsengineering/hermes > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:53:13): Unknown User (15:18:34): - Attachment: #2413 New package submission: healthyControlsPresenceChecker > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/davidechicco/healthyControlsPresenceChecker > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:18:35): Unknown User (15:25:23): - Attachment: #2414 healthyControlsPresenceChecker > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: davidechicco/healthyControlsPresenceChecker > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:25:25): Unknown User (15:26:50): - Attachment: #2415 healthyControlsPresenceChecker > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/davidechicco/healthyControlsPresenceChecker > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:26:53): Unknown User (15:36:32): - Attachment: #2416 healthyControlsPresenceChecker > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/davidechicco/healthyControlsPresenceChecker > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-11-02

Unknown User (01:01:24): - Attachment: #2417 QHScrnomo > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jixccf/QHScrnomo > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (01:01:26): Unknown User (01:16:52): - Attachment: #2418 QHScrnomo > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jixccf/QHScrnomo > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:57:13):

2021-11-05

Unknown User (10:27:35):

2021-11-08

Unknown User (08:31:18): - Attachment: #2419 DEPTH > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lsw123456789/DEPTH > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:31:19): Unknown User (08:45:01): - Attachment: #2420 DEPTH: An algorithm to quantify intratumor heterogeneity based on alterations of gene expression profiles > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/WangX-Lab/DEPTH > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:45:03): Unknown User (09:00:48): - Attachment: #2421 DEPTH: An algorithm to quantify intratumor heterogeneity based on alterations of gene expression profiles. > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/WangX-Lab/DEPTH > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:00:50): Unknown User (09:07:48): - Attachment: #2422 DEPTH: An algorithm to quantify intratumor heterogeneity based on alterations of gene expression profiles. > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/WangX-Lab/DEPTH > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:07:50): Unknown User (09:28:40): - Attachment: #2423 DEPTH: An algorithm to quantify intratumor heterogeneity based on alterations of gene expression profiles. > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/WangX-Lab/DEPTH > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:28:42): Unknown User (20:23:24): - Attachment: #2424 DEPTH: An algorithm to quantify intratumor heterogeneity based on alterations of gene expression profiles. > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/WangX-Lab/DEPTH > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (21:56:43): - Attachment: #2425 Rhisat > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Carla-Radames/Rhisat.git > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (21:56:44): Unknown User (22:04:31): - Attachment: #2426 Rhisat > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Carla-Radames/Rhisat > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-11-10

Unknown User (10:31:16): - Attachment: #2427 JASPAR2022 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/da-bar/JASPAR2022 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-11-16

Unknown User (08:26:40): Unknown User (08:29:27): Unknown User (09:16:08): Unknown User (09:16:10): Unknown User (09:16:11):

2021-11-18

Unknown User (04:44:59): - Attachment: #2428 DEPTH > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/WangX-Lab/DEPTH > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:45:06): Unknown User (12:23:58): - Attachment: #2429 Motif2Site package sumission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ManchesterBioinference/Motif2Site > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-11-22

Unknown User (09:12:50): - Attachment: #2430 prozor package submission > The package I am submitting is already on CRAN. I am happy to remove it once it is accepted for Bioconductor. > > > > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/protViz/prozor > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:12:52): Unknown User (12:13:53): - Attachment: #2431 OGRE submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/svenbioinf/OGRE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:07:35): - Attachment: #2432 prozor > Hi, > I did run BiocCheck and I know that there are two errors: > 1 “Package must be removed from CRAN.”
> 2 “Maintainer must register at the support site; visit https://support.bioconductor.org/accounts/signup/ .” > > > > > Ad 1 I am happy to remove it from CRAN once it is accepted for Bioconductor. > Ad 2 I am registered with https://support.bioconductor.org/accounts/signup/ with the e-mail provided in the package description. > > > > > > > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/protViz/prozor > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:07:37): Unknown User (15:10:40): - Attachment: #2433 prozor > Hi, > I did run BiocCheck and I know that there are two errors: > 1 “Package must be removed from CRAN.”
> 2 “Maintainer must register at the support site; visit https://support.bioconductor.org/accounts/signup/ .” > > > > > Ad 1 I am happy to remove it from CRAN once it is accepted for Bioconductor. > Ad 2 I am registered with https://support.bioconductor.org/accounts/signup/ with the e-mail provided in the package description. > > > > > > > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/protViz/prozor > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:28:12):

2021-11-23

Unknown User (07:30:31): Unknown User (09:33:10): - Attachment: #2434 prolfqua package > Hi, > I did run BiocCheck and I know that there are two errors: > 1 “Package must be removed from CRAN.”
> 2 “Maintainer must register at the support site; visit https://support.bioconductor.org/accounts/signup/ .” > > > > > Ad 1 I am happy to remove it from CRAN once it is accepted for Bioconductor. > Ad 2 I am registered with https://support.bioconductor.org/accounts/signup/ with the e-mail provided in the package description. > > > > > > > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/protViz/prozor > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-11-24

Unknown User (06:51:06): Unknown User (06:53:58): Unknown User (07:20:26): Unknown User (07:20:27): Unknown User (07:53:08): Unknown User (09:18:13): - Attachment: #2435 GenProSeq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/dongminjung/GenProSeq > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:18:15): Unknown User (09:41:06): - Attachment: #2436 GenProSeq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/dongminjung/GenProSeq > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:41:10): Unknown User (10:16:44):

2021-11-28

Unknown User (12:57:15): - Attachment: #2437 MetaboAnnotatoR package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/gggraca/MetaboAnnotatoR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:57:17):

2021-12-01

Unknown User (09:02:23): Unknown User (09:03:44): Unknown User (09:04:39):

2021-12-06

Unknown User (11:06:32): - Attachment: #2438 PanomiR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:06:33): Unknown User (11:08:19): - Attachment: #2439 PanomiR submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/pouryany/PanomiR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:08:22): Unknown User (11:19:50): - Attachment: #2440 PanomiR submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/pouryany/PanomiR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-12-07

Unknown User (03:32:50): - Attachment: #2441 Robust longitudinal Differential Expression (RolDE) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/elolab/RolDE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (03:32:52): Unknown User (04:18:40): - Attachment: #2442 RolDE (Robust longitudinal Differential Expression) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/elolab/RolDE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (06:19:53): - Attachment: #2443 MetaboAnnotation > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rformassspectrometry/MetaboAnnotation > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:51:18): Unknown User (07:51:20): Unknown User (13:42:06): - Attachment: #2444 TEKRABber submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: [https://github.com/ferygood/TEKRABber](https://github.com/ferygood/TEKRABber) > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:56:58): Unknown User (14:02:10): - Attachment: #2445 TEKRABber submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ferygood/TEKRABber > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:02:12): Unknown User (14:24:33): - Attachment: #2446 TEKRABber submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ferygood/TEKRABber > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:58:20): - Attachment: #2447 BSgenome.Gmax.EnsemblPlants > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Deisiany/BSgenome.Gmax.EnsemblPlants.Gmv2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:58:22):

2021-12-09

Unknown User (05:32:25): - Attachment: #2448 Ribostan > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/zslastman/Ribostan > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:29:45): - Attachment: #2449 CBEA Submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/qpmnguyen/CBEA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:45:18): - Attachment: #2450 MuData > • Repository: https://github.com/PMBio/MuDataMAE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:45:20):

2021-12-10

Unknown User (07:18:41): - Attachment: #2451 rgoslin submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lifs-tools/rgoslin > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic (lipidomic) data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:18:44): Unknown User (07:31:17): Unknown User (08:49:51): - Attachment: #2452 rgoslin submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lifs-tools/rgoslin > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:49:54):

2021-12-13

Unknown User (05:23:07): - Attachment: #2453 MuData > • Repository: https://github.com/ilia-kats/MuData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:45:34):

2021-12-15

Unknown User (04:56:29): - Attachment: #2454 protGear > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://keniajin.github.io/protGear/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:56:31): Unknown User (05:00:46): - Attachment: #2455 protGear > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Keniajin/protGear > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:00:48): Unknown User (05:03:35): - Attachment: #2456 protGear > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:03:37): Unknown User (05:04:56): - Attachment: #2457 protGear > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Keniajin/protGear > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:04:57): Unknown User (06:33:27): - Attachment: #2458 protGear > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Keniajin/protGear > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (06:33:29): Unknown User (06:39:11): - Attachment: #2459 protGear > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Keniajin/protGear > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (06:39:12): Unknown User (07:34:26): - Attachment: #2460 protGear > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Keniajin/protGear > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:04:39): - Attachment: #2461 LinTInd > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mana-W/LinTInd > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:04:41): Unknown User (12:34:31): Unknown User (12:34:32):

2021-12-17

Unknown User (22:04:25): - Attachment: #2462 crisprBowtie > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Jfortin1/crisprBowtie > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-12-18

Unknown User (06:31:36): - Attachment: #2463 APL package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (06:31:38): Unknown User (06:34:00): - Attachment: #2464 APL package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/VingronLab/APL > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (06:34:03): Unknown User (07:54:32): - Attachment: #2465 APL package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/VingronLab/APL > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-12-21

Unknown User (07:12:01): Unknown User (10:41:10):

2021-12-22

Unknown User (01:47:58): - Attachment: #2466 CompoundDb > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/EuracBiomedicalResearch/CompoundDb/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:26:45): - Attachment: #2467 MSA2dist > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/kullrich/MSA2dist > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:05:46):

2021-12-23

Unknown User (08:18:28): - Attachment: #2468 LinTInd > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mana-W/LinTInd > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-12-26

Unknown User (04:27:31): - Attachment: #2469 tinytools > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tidymass/tidymass > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:27:33): Unknown User (15:36:09): - Attachment: #2470 tinytools > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tidymass/tinytools > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2021-12-27

Unknown User (04:54:21): - Attachment: #2471 https://github.com/yasmina-mekki/gwhap > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:54:22): Unknown User (04:55:43): - Attachment: #2472 gwhap > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yasmina-mekki/gwhap > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:55:45):

2021-12-28

Unknown User (03:09:35): Unknown User (03:14:04): - Attachment: #2473 DEPTH > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/WangX-Lab/DEPTH > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (03:14:06): Unknown User (03:19:17): - Attachment: #2474 Deviating gene Expression Profiling Tumor Heterogeneity algorithm > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/WangX-Lab/DEPTH > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (03:19:19):

2022-01-03

Unknown User (08:12:01): Unknown User (23:28:16): - Attachment: #2475 poplin > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jaehyunjoo/poplin > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (23:28:17): Unknown User (23:43:38): - Attachment: #2476 poplin > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jaehyunjoo/poplin > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-01-05

Unknown User (07:43:15):

2022-01-06

Unknown User (02:01:37): - Attachment: #2477 CBNplot > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/noriakis/CBNplot > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (03:03:21): - Attachment: #2478 mbOmic > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/gongcongcong/mbOmic > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (03:03:24): Unknown User (03:52:27): - Attachment: #2479 mbOmic > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (03:52:29): Unknown User (03:53:36): - Attachment: #2480 mbOmic > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/gongcongcong/mbOmic > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (03:53:37): Unknown User (07:31:01): Unknown User (11:35:55): Unknown User (22:32:12): - Attachment: #2481 masstools > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tidymass/masstools > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-01-08

Unknown User (06:05:41): - Attachment: #2482 massconverter > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tidymass/massconverter > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-01-10

Unknown User (16:42:32): - Attachment: #2483 MACARRoN > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/biobakery/MACARRoN > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-01-11

Unknown User (12:28:05): - Attachment: #2484 rgoslin submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lifs-tools/rgoslin-bioc > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:28:07): Unknown User (12:34:10): - Attachment: #2485 rgoslin submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lifs-tools/rgoslin > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:43:09): - Attachment: #2486 CellWalkR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/PFPrzytycki/CellWalkR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-01-12

Unknown User (09:15:43): Unknown User (11:24:27): - Attachment: #2487 ExpressionSetViewer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mengchen18/ExpressionSetViewer > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-01-13

Unknown User (08:43:02): - Attachment: #2488 SPOTlight > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/MarcElosua/SPOTlight > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:09:55): Unknown User (10:11:35): - Attachment: #2489 DepInfeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lujunyan1118/DepInfeR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:11:37): Unknown User (10:21:22): - Attachment: #2490 DepInfeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lujunyan1118/DepInfeR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:21:23): Unknown User (13:49:27):

2022-01-14

Unknown User (04:01:59): - Attachment: #2491 rifi > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CyanolabFreiburg/rifi > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x]Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:02:01): Unknown User (04:29:01): - Attachment: #2492 rifi > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CyanolabFreiburg/rifi > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x]Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:14:23): - Attachment: #2493 xcore > • Repository: https://github.com/bkaczkowski/xcore > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:14:25): Unknown User (05:19:31): - Attachment: #2494 xcore > • Repository: https://github.com/bkaczkowski/xcore > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:19:32): Unknown User (05:29:27): - Attachment: #2495 DepInfeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Huber-group-EMBL/DepInfeR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:47:56): - Attachment: #2496 xcore > • Repository: https://github.com/bkaczkowski/xcore > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:10:37): - Attachment: #2497 MBECS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rmolbrich/MBECS > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor [Package Submission][2] > instructions. My package is consistent with the Bioconductor > [Package Guidelines][1]. > > • [x] I understand Bioconductor [Package Naming Policy][9] and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the [support site][3] for issues that users may > have, subscribing to the [bioc-devel][4] mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the [Bioconductor code of conduct][7] and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using [Git][5] > (optionally [via GitHub][6]). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the [Bioconductor website][8] to sign up.

Unknown User (15:06:48): - Attachment: #2498 CytoTalk > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tanlabcode/CytoTalk > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:28:16): - Attachment: #2499 updateObject > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Bioconductor/updateObject > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:28:17): Unknown User (16:08:28): - Attachment: #2500 beer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/athchen/beer > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:37:04): - Attachment: #2501 https://github.com/Deisiany/BSgenome.Gmax.EnsemblPlants.Gmv2.git > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository:https://github.com/Deisiany/BSgenome.Gmax.EnsemblPlants.Gmv2.git > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:37:05): Unknown User (16:50:51): - Attachment: #2502 https://github.com/Deisiany/BSgenome.Gmax.EnsemblPlants.Gmv2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository:https://github.com/Deisiany/BSgenome.Gmax.EnsemblPlants.Gmv2.git > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:50:52):

2022-01-15

Unknown User (14:06:38): - Attachment: #2503 PanViz submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/LucaAnholt/PanViz/tree/main/PanViz > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:06:40): Unknown User (14:19:02): - Attachment: #2504 PanViz submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/LucaAnholt/PanViz > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:19:04): Unknown User (14:21:32): - Attachment: #2505 PanViz submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository :https://github.com/LucaAnholt/PanViz > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-01-18

Unknown User (07:52:56): Unknown User (07:59:16): Unknown User (12:06:49): - Attachment: #2506 CytoTalk > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tanlabcode/CytoTalk > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:06:51): Unknown User (13:23:07): - Attachment: #2507 updateObject > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Bioconductor/updateObject > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:40:35): Unknown User (14:47:49): - Attachment: #2508 CytoTalk > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tanlabcode/CytoTalk > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-01-19

Unknown User (10:32:31): - Attachment: #2509 https://github.com/Deisiany/BSgenome.Gmax.EnsemblPlants.Gmv2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Deisiany/BSgenome.Gmax.EnsemblPlants.Gmv2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:32:34): Unknown User (10:50:25): - Attachment: #2510 https://github.com/Deisiany/BSgenome.Gmax.EnsemblPlants.Gmv2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Deisiany/BSgenome.Gmax.EnsemblPlants.Gmv2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:50:27):

2022-01-20

Unknown User (12:48:07):

2022-01-21

Unknown User (11:51:35): - Attachment: #2511 Rbwa > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Jfortin1/Rbwa > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-01-24

Unknown User (11:49:50): - Attachment: #2512 SUITOR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/wheelerb/SUITOR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:49:51): Unknown User (11:55:40): - Attachment: #2513 SUITOR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/wheelerb/SUITOR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:55:42): Unknown User (15:30:52): - Attachment: #2514 vitessceR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/vitessce/vitessceR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:30:54):

2022-01-25

Unknown User (08:49:58): - Attachment: #2515 SUITOR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/wheelerb/SUITOR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:09:53): - Attachment: #2516 vitessceR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/vitessce/vitessceR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-01-26

Unknown User (11:26:10): Unknown User (11:26:11):

2022-01-28

Megha Lal (11:13:59): > @Megha Lal has left the channel

Unknown User (12:57:16):

2022-02-01

Unknown User (08:24:37): - Attachment: #2517 UCSCRepeatMasker > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/functionalgenomics/UCSCRepeatMasker > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:24:38): Unknown User (08:25:52):

2022-02-02

Unknown User (10:34:30): Unknown User (10:34:31): Unknown User (10:34:34): Unknown User (11:19:21): - Attachment: #2518 MsBackendMsp > Short info: MsBackendMsp adds support for files in MSP format to the Spectra Bioconductor package and hence allows to import and export mass spectrometry data from (to) such files. > > > > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/RforMassSpectrometry/MsBackendMsp > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-02-03

Unknown User (16:16:22): - Attachment: #2519 UCell > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/carmonalab/UCell > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:16:24): Unknown User (17:02:16): - Attachment: #2520 UCell > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/carmonalab/UCell > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-02-04

Unknown User (06:47:22): - Attachment: #2521 bandle > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ococrook/bandle > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:42:36): Unknown User (07:44:14): Unknown User (07:53:31): Unknown User (12:32:08): - Attachment: #2522 cellxgenedp > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mtmorgan/cellxgenedp > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-02-07

Unknown User (10:29:22):

2022-02-08

Unknown User (08:24:46): - Attachment: #2523 omicsViewer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mengchen18/omicsViewer > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:26:47): Unknown User (08:29:54): Unknown User (08:29:56): Unknown User (21:58:41): - Attachment: #2524 ASURAT > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/keita-iida/ASURAT > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-02-11

Unknown User (10:21:04): - Attachment: #2525 MobilityTransformR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/LiesaSalzer/MobilityTransformR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:21:06): Unknown User (11:00:39): - Attachment: #2526 MobilityTransformR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/LiesaSalzer/MobilityTransformR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-02-12

Unknown User (12:38:14): - Attachment: #2527 single > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rocioespci/single > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:38:16):

2022-02-14

Unknown User (15:09:18): - Attachment: #2528 single > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rocioespci/single > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-02-15

Unknown User (09:46:41): - Attachment: #2529 PSMatch > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rformassspectrometry/PSMatch > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Daniela Cassol (13:31:06): > @Daniela Cassol has left the channel

Unknown User (17:37:33): - Attachment: #2530 STdeconvolve > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/JEFworks-Lab/STdeconvolve > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-02-17

Unknown User (08:49:03): Unknown User (08:49:07): Unknown User (08:49:09):

2022-02-18

Unknown User (05:59:09): - Attachment: #2531 pareg > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/cbg-ethz/pareg > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (21:43:26): - Attachment: #2532 gemma.R > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/PavlidisLab/gemma.R > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (21:43:28):

2022-02-22

Unknown User (07:51:05):

2022-02-23

Unknown User (01:58:08): - Attachment: #2533 gemma.R > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/PavlidisLab/gemma.R > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:09:33): - Attachment: #2534 pareg > Note: my old submission was rejected due to “The package DESCRIPTION must contain a biocViews field with one or more > valid biocViews terms.” which I find confusing because my DESCRIPTION has a biocViews field with valid terms. > Running BiocCheck::BiocCheck('new-package'=TRUE) locally also shows no problems with DESCRIPTION. > When comparing my project to a few others I noticed that I am using the master branch while others use the main branch. But the official docs also use the master branch, so this shouldn’t be an issue, right? > > > > > ————————- > > > > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/cbg-ethz/pareg > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:09:35): Unknown User (08:13:49): - Attachment: #2535 pareg > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/cbg-ethz/pareg > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:13:51): Unknown User (08:36:05): - Attachment: #2536 pareg > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/cbg-ethz/pareg > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:36:07): Unknown User (08:38:01): - Attachment: #2537 pareg > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/cbg-ethz/pareg > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:59:34): - Attachment: #2538 protlocassign > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mooredf22/protlocassign > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming > > > > > Comments on notes: > The “protlocassign” package contains a suite of R programs for using mass spectrometry data from differential fractionation experiments to assign proteins to subcellular compartments. The method can proportionally assign proteins resident in more than one subcellular compartment. This package includes seven vignettes describing in detail how to use the package and interpret the results. There is also an accompanying manuscript currently in revision for publication. Here are comments on the notes produced by “biocCheck”: > $note > 1 “Consider adding these automatically suggested biocViews: RNASeq” > This is not relevant to our proteomic data. > > > > > 2 “Recommended function length 3”Consider adding runnable examples to the following man pages which document exported objects:” > The listed man pages do not lend themselves easily to a runnable example. The accompanying vignettes demonstrate > in detail how to prepare data for these plots. > > > > > 4 “Consider shorter lines; 235 lines (3%) are ](https://support.bioconductor.org)”Consider adding runnable examples to the following man pages which document exported objects:” > The listed man pages do not lend themselves easily to a runnable example. The accompanying vignettes demonstrate > in detail how to prepare data for these plots. > > > > > 4 “Consider shorter lines; 235 lines (3%) are ) 80 characters long.”
> All lines in functions are 5 “Consider multiples of 4 spaces for line indents, 1130 lines(15%) are not.”
> We have chosen descriptive variable names to allow one to easily connect them and their meaning with the text in the vignettes and in the accompanying manuscript (revision under review). This has resulted in variable names that are unusually long, and > thus we believe that the spacing we have used (not always multiples of 4) makes the code easier to read and also to keep lines > less than 80 characters long. > > > > > 6 “Cannot determine whether maintainer is subscribed to the bioc-devel mailing list (requires admin credentials). Subscribe\nhere: <https://stat.ethz.ch/mailman/listinfo/bioc-devel” > I](http://bioconductor.org/developers/how-to/git/) “Consider multiples of 4 spaces for line indents, 1130 lines(15%) are not.”
> We have chosen descriptive variable names to allow one to easily connect them and their meaning with the text in the vignettes and in the accompanying manuscript (revision under review). This has resulted in variable names that are unusually long, and > thus we believe that the spacing we have used (not always multiples of 4) makes the code easier to read and also to keep lines > less than 80 characters long. > > > > > 6 “Cannot determine whether maintainer is subscribed to the bioc-devel mailing list (requires admin credentials). Subscribe\nhere: <https://stat.ethz.ch/mailman/listinfo/bioc-devel” > I) signed up as a maintainer. I don’t understand why biocCheck can’t verify this.

Unknown User (15:59:36):

2022-02-25

Unknown User (07:38:09):

2022-02-26

Unknown User (10:12:10): - Attachment: #2539 protlocassign > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming > > > > > Comments: > The “protlocassign” package presents R functions that take use mass spectrometry data from serial fractionation experiments to proportionally assign proteins to possibly multiple residences in subcellular organelles. The package includes seven vignettes that describe the methods in detail. There is also an accompanying manuscript describing the methods; a revision is under review. > > > > > Here are my comments on BiocCheck notes: > > > > > 1 “Consider adding these automatically suggested biocViews: RNASeq”
> This is not relevant to this proteomics-related package > > > > > 2 “Recommended function length 3”Consider adding runnable examples to the following man pages which document exported objects:“
> Most of the functions that are not service functions include runnable examples. The small number that are not are explained and illustrated in detail in the accompanying vignettes; setting up runnable examples for these functions withing the help files would be cumbersome. > > > > > 4”Consider shorter lines; 235 lines (3%) are ](https://support.bioconductor.org) “Consider adding runnable examples to the following man pages which document exported objects:”
> Most of the functions that are not service functions include runnable examples. The small number that are not are explained and illustrated in detail in the accompanying vignettes; setting up runnable examples for these functions withing the help files would be cumbersome. > > > > > 4 “Consider shorter lines; 235 lines (3%) are ) 80 characters long.”
> All lines in the functions are shorter than 80 characters. Much of the explanatory text in the vignettes are longer than 80 characters, and we believe that that text is readable and clear in its current form. > > > > > 5 “Consider multiples of 4 spaces for line indents, 1133 lines(15%) are not.”
> We have chosen to use descriptive variable names in our code in order to clearly link them to the to the concepts explained in the vignettes and in the accompanying manuscript. As a consequence, some of these variable names are rather long, which makes it difficult to adhere strictly to the “multiples of 4 spaces” suggestion. We have chosen indentation amounts to be as readable as possible and also conform to the limit of 80 characters per line. > > > > > 6 “Cannot determine whether maintainer is subscribed to the bioc-devel mailing list (requires admin credentials).\nSubscribe here: https://stat.ethz.ch/mailman/listinfo/bioc-devel” > I am listed as the maintainer and I have subscribed to this mailing list.

Unknown User (19:11:00): Unknown User (20:31:58): - Attachment: #2540 protlocassign > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mooredf22/protlocassign > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming > > > > > Comments: > The “protlocassign” package presents R functions that take use mass spectrometry data from serial fractionation experiments to proportionally assign proteins to possibly multiple residences in subcellular organelles. The package includes seven vignettes that describe the methods in detail. There is also an accompanying manuscript describing the methods; a revision is under review. > > > > > Here are my comments on BiocCheck notes: > > > > > 1 “Consider adding these automatically suggested biocViews: RNASeq”
> This is not relevant to this proteomics-related package > > > > > 2 “Recommended function length 3”Consider adding runnable examples to the following man pages which document exported objects:“
> Most of the functions that are not service functions include runnable examples. The small number that are not are explained and illustrated in detail in the accompanying vignettes; setting up runnable examples for these functions withing the help files would be cumbersome. > > > > > 4”Consider shorter lines; 235 lines (3%) are ](https://support.bioconductor.org) “Consider adding runnable examples to the following man pages which document exported objects:”
> Most of the functions that are not service functions include runnable examples. The small number that are not are explained and illustrated in detail in the accompanying vignettes; setting up runnable examples for these functions withing the help files would be cumbersome. > > > > > 4 “Consider shorter lines; 235 lines (3%) are ) 80 characters long.”
> All lines in the functions are shorter than 80 characters. Much of the explanatory text in the vignettes are longer than 80 characters, and we believe that that text is readable and clear in its current form. > > > > > 5 “Consider multiples of 4 spaces for line indents, 1133 lines(15%) are not.”
> We have chosen to use descriptive variable names in our code in order to clearly link them to the to the concepts explained in the vignettes and in the accompanying manuscript. As a consequence, some of these variable names are rather long, which makes it difficult to adhere strictly to the “multiples of 4 spaces” suggestion. We have chosen indentation amounts to be as readable as possible and also conform to the limit of 80 characters per line. > > > > > 6 “Cannot determine whether maintainer is subscribed to the bioc-devel mailing list (requires admin credentials).\nSubscribe here: https://stat.ethz.ch/mailman/listinfo/bioc-devel” > I am listed as the maintainer and I have subscribed to this mailing list.

Unknown User (20:31:59): Unknown User (21:11:45): - Attachment: #2541 protlocassign > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mooredf22/protlocassign > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming > > > > > Comments: > The “protlocassign” package presents R functions that take use mass spectrometry data from serial fractionation experiments to proportionally assign proteins to possibly multiple residences in subcellular organelles. The package includes seven vignettes that describe the methods in detail. There is also an accompanying manuscript describing the methods; a revision is under review. > > > > > Here are my comments on BiocCheck notes: > > > > > 1 “Consider adding these automatically suggested biocViews: RNASeq”
> This is not relevant to this proteomics-related package > > > > > 2 “Recommended function length 3”Consider adding runnable examples to the following man pages which document exported objects:“
> Most of the functions that are not service functions include runnable examples. The small number that are not are explained and illustrated in detail in the accompanying vignettes; setting up runnable examples for these functions withing the help files would be cumbersome. > > > > > 4”Consider shorter lines; 235 lines (3%) are ](https://support.bioconductor.org) “Consider adding runnable examples to the following man pages which document exported objects:”
> Most of the functions that are not service functions include runnable examples. The small number that are not are explained and illustrated in detail in the accompanying vignettes; setting up runnable examples for these functions withing the help files would be cumbersome. > > > > > 4 “Consider shorter lines; 235 lines (3%) are ) 80 characters long.”
> All lines in the functions are shorter than 80 characters. Much of the explanatory text in the vignettes are longer than 80 characters, and we believe that that text is readable and clear in its current form. > > > > > 5 “Consider multiples of 4 spaces for line indents, 1133 lines(15%) are not.”
> We have chosen to use descriptive variable names in our code in order to clearly link them to the to the concepts explained in the vignettes and in the accompanying manuscript. As a consequence, some of these variable names are rather long, which makes it difficult to adhere strictly to the “multiples of 4 spaces” suggestion. We have chosen indentation amounts to be as readable as possible and also conform to the limit of 80 characters per line. > > > > > 6 “Cannot determine whether maintainer is subscribed to the bioc-devel mailing list (requires admin credentials).\nSubscribe here: https://stat.ethz.ch/mailman/listinfo/bioc-devel” > I am listed as the maintainer and I have subscribed to this mailing list.

2022-03-01

Unknown User (09:17:05):

2022-03-03

Unknown User (00:30:02): - Attachment: #2542 nnSVG > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lmweber/nnSVG > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (00:30:04): Unknown User (00:38:37): - Attachment: #2543 nnSVG > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lmweber/nnSVG > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:03:38): Unknown User (17:45:16): - Attachment: #2544 Macarron > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/biobakery/Macarron > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:45:19):

2022-03-04

Unknown User (07:13:48): - Attachment: #2545 GRaNIEData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/chrarnold/GRaNIEData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:13:50): Unknown User (07:54:42): Unknown User (11:54:07): - Attachment: #2546 Macarron > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/biobakery/Macarron > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:41:03): - Attachment: #2547 ATACCoGAPS > • Repository: https://github.com/FertigLab/ATACCoGAPS > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:41:05): Unknown User (13:02:20): - Attachment: #2548 ATACCoGAPS > • Repository: https://github.com/FertigLab/ATACCoGAPS > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:42:01): - Attachment: #2549 GRaNIE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/chrarnold/GRaNIE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:42:03): Unknown User (20:48:29): - Attachment: #2550 GRaNIE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/chrarnold/GRaNIE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:48:31):

2022-03-05

Unknown User (13:16:58): - Attachment: #2551 GRaNIE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/chrarnold/GRaNIE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:16:59): Unknown User (13:18:36): - Attachment: #2552 GRaNIE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/chrarnold/GRaNIE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:18:37):

2022-03-06

Unknown User (04:13:05): - Attachment: #2553 ScreenR package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/EmanuelSoda/ScreenR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:13:06): Unknown User (04:15:31): - Attachment: #2554 ScreenR package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/EmanuelSoda/ScreenR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:15:33): Unknown User (04:21:26): - Attachment: #2555 ScreenR package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/EmanuelSoda/ScreenR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-03-07

Unknown User (07:21:47): Unknown User (08:11:39): Unknown User (08:11:43): Unknown User (08:16:19): Unknown User (08:16:39): Unknown User (08:17:46): Unknown User (08:22:04): Unknown User (08:22:21): Unknown User (08:27:38): Unknown User (08:28:41): Unknown User (09:07:20): Unknown User (09:32:46): - Attachment: #2556 GRaNIE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/chrarnold/GRaNIE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:30:44): - Attachment: #2557 ATACCoGAPS > • Repository: https://github.com/FertigLab/ATACCoGAPS > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:08:26): - Attachment: #2558 EpiMix > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/gevaertlab/EpiMix.data > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:01:55):

2022-03-09

Unknown User (06:34:22): Unknown User (08:13:18): Unknown User (08:13:20):

2022-03-10

Unknown User (09:56:43):

2022-03-11

Unknown User (06:25:32): Unknown User (06:25:38): Unknown User (08:36:57): Unknown User (08:41:19):

2022-03-13

Unknown User (08:26:51): - Attachment: #2559 cogeqc > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/almeidasilvaf/cogeqc > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-03-14

Unknown User (10:57:04): Unknown User (10:57:54): Unknown User (13:32:55): - Attachment: #2560 interactionHub > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jianhong/interactionHub > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:17:35): Unknown User (15:22:18): - Attachment: #2561 GenomicInteractionHub > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jianhong/GenomicInteractionHub > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-03-15

Unknown User (05:03:14): - Attachment: #2562 ExperimentList > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/DavisLaboratory/ExperimentList > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:03:16): Unknown User (05:09:40): - Attachment: #2563 ExperimentList > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/DavisLaboratory/ExperimentList > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:40:21): Unknown User (08:42:36): - Attachment: #2564 biodbExpasy extension package for biodb > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/pkrog/biodbExpasy > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-03-16

Unknown User (22:45:26): - Attachment: #2565 卡卡卡啊 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:45:28):

2022-03-17

Unknown User (07:20:02): Unknown User (08:16:07): - Attachment: #2566 biodbNcbi extension package for biodb > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/pkrog/biodbNcbi > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:27:48): - Attachment: #2567 qmtools > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/HimesGroup/qmtools > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:32:10): Unknown User (20:35:19): - Attachment: #2568 EpiCompare > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/neurogenomics/EpiCompare > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-03-18

Unknown User (07:18:14): - Attachment: #2569 ggtranscript > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/dzhang32/ggtranscript > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:40:23): - Attachment: #2570 cytoMEM > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/cytolab/cytoMEM > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-03-20

Unknown User (12:23:01): - Attachment: #2571 RAREsim > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/meganmichelle/RAREsim > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (21:32:16): - Attachment: #2572 seqArchR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/snikumbh/seqArchR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (21:38:29): - Attachment: #2573 standR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/DavisLaboratory/standR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (21:38:31): Unknown User (21:48:08): - Attachment: #2574 standR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/DavisLaboratory/standR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (21:51:09): - Attachment: #2575 fastreeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/gkanogiannis/fastreeR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-03-21

Unknown User (14:17:43): - Attachment: #2576 TREG > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/LieberInstitute/TREG > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:19:50): Unknown User (14:19:51): Unknown User (14:19:54): Unknown User (14:19:55): Unknown User (14:19:57): Unknown User (14:19:59): Unknown User (23:43:38): - Attachment: #2577 SignacSlim > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Honchkrow/SignacSlim > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (23:43:41):

2022-03-22

Unknown User (03:46:48): - Attachment: #2578 biodbMirbase extension package for biodb > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/pkrog/biodbMirbase > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:47:07): - Attachment: #2579 biodbNci extension package for biodb > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/pkrog/biodbNci > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:17:45): - Attachment: #2580 unable to deploy shiny app to shinyapp.io (Bioconductor source) > Hi, > I have the same problem as in this post that had no answers. > Basically, when I try to deploy my InteractiveComplexHeatmap, the action is interrupted > > > > > > Error: Unhandled Exception: Child Task 1121686583 failed: Error parsing manifest: Unable to determine package source for Bioconductor package BiocGenerics: Repository must be specified > > Execution halted > > > > > Any suggestions would be appreciated, thanks!

Unknown User (11:17:47): Unknown User (11:23:09): - Attachment: #2581 unable to deploy shiny app to shinyapp.io (Bioconductor source) > repository https://github.com/jokergoo/InteractiveComplexHeatmap > Hi, > I have the same problem as in this post that had no answers. > Basically, when I try to deploy my InteractiveComplexHeatmap, the action is interrupted > > > > > > Error: Unhandled Exception: Child Task 1121686583 failed: Error parsing manifest: Unable to determine package source for Bioconductor package BiocGenerics: Repository must be specified > > Execution halted > > > > > Any suggestions would be appreciated, thanks!

Unknown User (11:23:11): Unknown User (17:42:20): - Attachment: #2582 crisprBwa > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[crisprBwa]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:42:22): Unknown User (17:43:09): - Attachment: #2583 crisprBwa > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Jfortin1/crisprBwa > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-03-23

Unknown User (00:30:58): - Attachment: #2584 ompBAM > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/alexchwong/ompBAM > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Lukas Weber (11:40:36): > @Lukas Weber has joined the channel

Unknown User (14:09:13): - Attachment: #2585 scMET: Bayesian modelling of DNA methylation heterogeneity at single-cell resolution > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/andreaskapou/scMET > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Quang Nguyen (17:10:22): > @Quang Nguyen has joined the channel

2022-03-24

Unknown User (08:18:30): - Attachment: #2586 InterTADs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BiodataAnalysisGroup/InterTADs > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:18:31): Unknown User (08:21:56): - Attachment: #2587 InterTADs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BiodataAnalysisGroup/InterTADs > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:21:58): Unknown User (09:05:27): - Attachment: #2588 InterTADs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BiodataAnalysisGroup/InterTADs > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:05:30): Unknown User (12:27:03):

2022-03-25

Unknown User (16:58:15): - Attachment: #2589 VectraPolarisData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/julia-wrobel/VectraPolarisData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:58:17): Unknown User (17:01:15): - Attachment: #2590 VectraPolarisData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/julia-wrobel/VectraPolarisData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:01:17): Unknown User (17:02:44): - Attachment: #2591 VectraPolarisData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/julia-wrobel/VectraPolarisData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:02:45):

2022-03-26

Unknown User (09:33:26): - Attachment: #2592 SignacSlim > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Honchkrow/SignacSlim > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:56:16): - Attachment: #2593 VectraPolarisData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/julia-wrobel/VectraPolarisData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:56:18):

2022-03-27

Unknown User (22:21:06): - Attachment: #2594 VectraPolarisData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/julia-wrobel/VectraPolarisData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:45:12): - Attachment: #2595 kataegis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:45:13):

2022-03-28

Unknown User (03:52:46): - Attachment: #2596 tomoseqr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/bioinfo-tsukuba/tomoseqr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (03:52:49): Unknown User (04:03:58): - Attachment: #2597 tomoseqr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/bioinfo-tsukuba/tomoseqr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:54:17): - Attachment: #2598 extraChIPs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/steveped/extraChIPs > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-03-30

Unknown User (07:52:42): - Attachment: #2599 sSNAPPY > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Wenjun-Liu/sSNAPPY > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:05:38): Unknown User (08:05:43): Unknown User (08:05:45): Unknown User (08:05:47):

2022-03-31

Unknown User (07:46:16): Unknown User (18:37:40): - Attachment: #2600 NanoStringExperiment > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Nanostring-Biostats/NanoStringExperiment > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:37:42): Unknown User (18:41:25): - Attachment: #2601 NanoStringExperiment > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Nanostring-Biostats/NanoStringExperiment > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:41:27): Unknown User (18:47:04): - Attachment: #2602 NanoStringExperiment > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Nanostring-Biostats/NanoStringExperiment > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:56:49): - Attachment: #2603 SpatialOmicsOverlay > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Nanostring-Biostats/SpatialOmicsOverlay > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:56:50): Unknown User (20:09:52): - Attachment: #2604 SpatialOmicsOverlay > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Nanostring-Biostats/SpatialOmicsOverlay > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (21:53:47): - Attachment: #2605 SPIAT > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/TrigosTeam/spaSim > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (21:54:35): Unknown User (21:55:40): - Attachment: #2606 SPIAT > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/TrigosTeam/SPIAT > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:31:15): - Attachment: #2607 spaSim > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/TrigosTeam/spaSim > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:31:19): Unknown User (22:33:23):

2022-04-01

Unknown User (00:44:51): - Attachment: #2608 Submitting a new package cfTools > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jasminezhoulab/cfTools > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (06:06:00): - Attachment: #2609 consICA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/biomod-lih/consICA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:49:23): - Attachment: #2610 stJoincount > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Nina-Song/stJoincount > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:50:59): - Attachment: #2611 DifferentialRegulation > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SimoneTiberi/DifferentialRegulation > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:55:45): - Attachment: #2612 qsvaR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/LieberInstitute/qsvaR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:59:39): - Attachment: #2613 borealis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/GarrettJenkinson/borealis > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:59:41): Unknown User (14:07:13): - Attachment: #2614 borealis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/GarrettJenkinson/borealis > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org/ > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:18:24): - Attachment: #2615 terraTCGAdata > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/waldronlab/terraTCGAdata > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:18:26): Unknown User (18:25:48): - Attachment: #2616 terraTCGAdata > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/waldronlab/terraTCGAdata > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (19:02:42): - Attachment: #2617 BiocUtils > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Bioconductor/BiocUtils > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-04-05

Unknown User (07:51:53): Unknown User (08:04:42): Unknown User (09:50:03): Unknown User (09:50:05): Unknown User (09:50:07): Unknown User (09:50:08): Unknown User (09:50:10): Unknown User (09:50:11): Unknown User (09:50:13): Unknown User (09:50:14):

2022-04-06

Unknown User (21:34:54):

2022-04-07

Unknown User (17:02:45): - Attachment: #2618 Drosophila simulans BSgenome forge package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/stupornova33/BSgenome.Dsimulans > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:02:47): Unknown User (17:04:06): - Attachment: #2619 BSGenome.Dsimulans.NCBI.3.1.fa > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:04:08): Unknown User (17:05:44): - Attachment: #2620 BSGenome.Dsimulans.NCBI.3.1.fa > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/stupornova33/BSgenome.Dsimulans > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:05:46): Unknown User (17:13:54): - Attachment: #2621 https://github.com/stupornova33/BSgenome.Dsimulans.NCBI.3.1.fa > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:13:55): Unknown User (17:15:28): - Attachment: #2622 BSgenome.Dsimulans.NCBI.3.1.fa > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/stupornova33/BSgenome.Dsimulans.NCBI.3.1.fa.git > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:15:29): Unknown User (17:16:39): - Attachment: #2623 BSgenome.Dsimulans.NCBI.3.1.fa > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/stupornova33/BSgenome.Dsimulans.NCBI.3.1.fa > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:16:41): Unknown User (17:18:18): - Attachment: #2624 BSGenome.Dsimulans.NCBI.3.1.fa > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/stupornova33/BSGenome.Dsimulans.NCBI.3.1.fa > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:18:20):

2022-04-08

Unknown User (01:21:29): Unknown User (01:35:13): Unknown User (04:06:30): - Attachment: #2625 SimBu > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/omnideconv/SimBu > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:06:32): Unknown User (04:09:48): - Attachment: #2626 SimBu > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/omnideconv/SimBu > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:09:50): Unknown User (04:17:27): - Attachment: #2627 SimBu > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/omnideconv/SimBu > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:17:13): Unknown User (14:17:14): Unknown User (14:17:16): Unknown User (14:17:17): Unknown User (14:17:18): Unknown User (14:38:17): - Attachment: #2628 New package: zenith > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: http://diseaseneurogenomics.github.io/zenith/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:38:19): Unknown User (14:41:53): - Attachment: #2629 zenith - try2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/DiseaseNeuroGenomics/zenith/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:41:55): Unknown User (14:54:55): - Attachment: #2630 zenith - try3 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/DiseaseNeuroGenomics/zenith/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-04-11

Unknown User (03:55:01): - Attachment: #2631 LipidSigR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/TMSWCChenglab/LipidSigR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:51:40): - Attachment: #2632 ccImpute software package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/khazum/ccImpute > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (19:47:03): - Attachment: #2633 GenomicInteractionNodes > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jianhong/GenomicInteractionNodes > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (21:10:09): Unknown User (21:11:44): - Attachment: #2634 BiocDevelUtils > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Bioconductor/BiocDevelUtils > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-04-12

Unknown User (04:09:22): - Attachment: #2635 RgnTX > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yue-wang-biomath/RgnTX > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:37:37): - Attachment: #2636 SpotClean > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/zijianni/SpotClean > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:37:40): Unknown User (11:48:25): - Attachment: #2637 SpotClean > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/zijianni/SpotClean > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:19:38): - Attachment: #2638 protlocassign > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > Repository: https://github.com/mooredf22/protlocassign > Confirm the following by editing each check box to ‘[x]’ > > > > > I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > > > > I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > > > > I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > > > > I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > the package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > > > > My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > > > > I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > The ‘devel’ branch for new packages and features. > The stable ‘release’ branch, is made available every six > months, for bug fixes. > Bioconductor version control using Git > (optionally via GitHub). > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > Comments: > The “protlocassign” package presents R functions that take use mass spectrometry data from serial fractionation experiments to proportionally assign proteins to possibly multiple residences in subcellular organelles. The package includes a set of seven tutorials, comprising a vignette, that describes the methods in detail. There is also an accompanying manuscript describing the methods; a revision is under review. > > > > > I request that this submission, #2541, be re-opened. We have re-worked this package extensively to make it suitable for Bioconductor. In particular, while previously we had seven vignettes, we have now combined them into a single file, and refer to them as tutorials. We have also eliminated many figures. In this way, we have reduced the package size considerably. On my Windows machine, the package binary is 2.34 MB and the vignette (tutorials) is 2.54 MB. We have considerably re-worked the help files and added unit tests. This also has reduced the build time. > > > > > The vignette (tutorials) corresponds to those we are using as supplemental material for a manuscript currently under review. We hope that the current size is satisfactory so that it will correspond closely with the version in our manuscript.

Unknown User (16:19:40):

2022-04-13

Unknown User (17:51:55):

2022-04-14

Unknown User (07:59:47): Unknown User (11:24:58): - Attachment: #2639 InterTADs package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BiodataAnalysisGroup/InterTADs > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-04-15

Unknown User (10:38:11): Unknown User (10:39:24): - Attachment: #2640 BiocDeveloper > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Bioconductor/BiocDeveloper > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:20:47):

2022-04-18

Unknown User (09:02:31): Unknown User (09:02:32): Unknown User (09:02:33): Unknown User (09:02:34): Unknown User (09:02:36): Unknown User (09:02:38): Unknown User (09:02:39): Unknown User (09:02:40): Unknown User (09:02:41): Unknown User (09:47:59): Unknown User (09:54:52): Unknown User (09:59:22): Unknown User (11:21:12): Unknown User (23:04:35): - Attachment: #2641 sciCNV > Update the following URL to point to the GitHub repository of > https://github.com/alimahdipour/sciCNV > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (23:04:36): Unknown User (23:08:53): - Attachment: #2642 sciCNV > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/alimahdipour/sciCNV > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (23:08:55):

2022-04-19

Unknown User (05:01:59): - Attachment: #2643 oncoscanR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yannchristinat/oncoscanR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:02:01): Unknown User (05:06:19): - Attachment: #2644 oncoscanR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yannchristinat/oncoscanR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:34:15): - Attachment: #2645 sciCNV > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/alimahdipour/sciCNV > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:34:18): Unknown User (10:38:23): Unknown User (14:39:03):

2022-04-20

Unknown User (14:31:30): Unknown User (14:32:50): rohitsatyam102 (16:32:33): > @rohitsatyam102 has joined the channel

2022-04-21

Unknown User (03:07:29): Unknown User (03:07:34): Unknown User (22:21:51): - Attachment: #2646 BiocBaseUtils > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Bioconductor/BiocBaseUtils > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-04-22

Unknown User (15:15:09): Unknown User (15:15:10): Unknown User (15:15:11): Unknown User (15:15:13): Unknown User (15:15:14): Unknown User (15:15:15): Unknown User (15:15:16): Unknown User (15:15:17): Unknown User (15:15:19): Unknown User (15:15:20): Unknown User (15:15:21):

2022-04-24

Unknown User (06:04:44):

2022-04-25

Unknown User (09:58:17): Unknown User (10:28:38): Unknown User (10:28:39): Unknown User (10:28:41): Unknown User (10:28:42): Unknown User (10:28:44): Unknown User (10:28:45): Unknown User (10:28:47):

2022-04-26

Unknown User (11:21:54): - Attachment: #2647 crisprDesign > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Jfortin1/crisprDesign > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (19:59:42): - Attachment: #2648 IFAA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/quranwu/IFAA.git > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (19:59:43): Unknown User (20:01:22): - Attachment: #2649 IFAA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/quranwu/IFAA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:01:24): Unknown User (20:05:26): - Attachment: #2650 IFAA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/quranwu/IFAA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:05:27): Unknown User (20:12:50): - Attachment: #2651 IFAA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/quranwu/IFAA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-04-27

Unknown User (15:40:40): - Attachment: #2652 IMPACC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/DataSlingers/IMPACC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:40:42): Unknown User (15:44:29): - Attachment: #2653 IMPACC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/DataSlingers/IMPACC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:44:31): Unknown User (15:51:42): - Attachment: #2654 IMPACC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/DataSlingers/IMPACC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:51:44): Unknown User (16:00:18): - Attachment: #2655 IMPACC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/DataSlingers/IMPACC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-04-29

Unknown User (17:08:45): - Attachment: #2656 protlocassigndoc > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mooredf22/protlocassigndoc > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming > > > > > # # # > > This is a workflow package that is connected to the “protlocassign” package, Issue #2541. Since this workflow package consists of more extensive documentation than can fit in the protlocassign package, these two submissions should be considered together.

2022-05-04

Unknown User (08:41:29): - Attachment: #2657 goSorensen > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/pablof1988/goSorensen > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:41:31):

2022-05-05

Unknown User (19:09:22): - Attachment: #2658 goSorensen > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/pablof1988/goSorensen > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-05-06

Unknown User (07:24:12): Sean Davis (14:24:31): > @Sean Davis has left the channel

2022-05-09

Unknown User (18:04:58): - Attachment: #2659 proteasy > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/martinry/proteasy > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:05:01): Unknown User (18:12:26): - Attachment: #2660 proteasy > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/martinry/proteasy > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-05-10

Unknown User (13:29:01):

2022-05-11

Unknown User (13:13:44): Unknown User (13:13:46): - Attachment: #2661 PALMO package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/aifimmunology/PALMO > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (19:28:07):

2022-05-12

Unknown User (10:59:45): Unknown User (11:00:20): Unknown User (11:45:29): - Attachment: #2662 goSorensen > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/pablof1988/goSorensen > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:45:33): Unknown User (13:46:04):

2022-05-18

Unknown User (05:36:44): - Attachment: #2663 CTSV > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jingeyu/CTSV > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-05-20

Unknown User (05:41:42): - Attachment: #2664 katdetectr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/daanhazelaar/katdetectr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-05-23

Unknown User (00:29:21): - Attachment: #2665 omada > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BioSok/omada > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (00:29:23): Unknown User (04:31:23): - Attachment: #2666 omada > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BioSok/omada > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:31:25): Unknown User (04:39:32): - Attachment: #2667 omada > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BioSok/omada > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:39:35): Unknown User (05:49:41): - Attachment: #2668 omada > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BioSok/omada > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:01:08): Unknown User (10:02:25): - Attachment: #2669 mslp > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ccshao/mslp > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:13:23): - Attachment: #2670 katdetectr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ErasmusMC-CCBC/katdetectr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:13:25): Unknown User (16:15:20): - Attachment: #2671 katdetectr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ErasmusMC-CCBC/katdetectr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:15:22): Unknown User (16:18:28): - Attachment: #2672 katdetectr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ErasmusMC-CCBC/katdetectr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:18:31): Unknown User (16:21:12): - Attachment: #2673 Katdetectr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ErasmusMC-CCBC/katdetectr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:21:14): Unknown User (16:24:15): - Attachment: #2674 katdetectr(rename) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ErasmusMC-CCBC/katdetectr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:24:18): Unknown User (16:25:56): - Attachment: #2675 KataegisDetectr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ErasmusMC-CCBC/katdetectr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:25:59):

2022-05-24

Unknown User (07:37:48): - Attachment: #2676 katdetectr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ErasmusMC-CCBC/katdetectr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:15:24): - Attachment: #2677 GenomAutomorphism > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/genomaths/GenomAutomorphism > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:15:26): Unknown User (16:40:18): - Attachment: #2678 GenomAutomorphism > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/genomaths/GenomAutomorphism > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-05-25

Unknown User (13:50:09): - Attachment: #2679 ATACseqTFEA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jianhong/ATACseqTFEA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-05-26

Unknown User (11:09:05): - Attachment: #2680 eds > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/k3yavi/eds > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-05-27

Unknown User (12:48:32): Unknown User (12:48:34): Unknown User (12:48:36): Unknown User (12:48:37):

2022-05-30

Unknown User (01:34:16): - Attachment: #2681 speckle > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/phipsonlab/speckle > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (01:34:19):

2022-05-31

Unknown User (02:53:05): - Attachment: #2682 syntenet > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/almeidasilvaf/syntenet > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-06-01

Unknown User (14:08:37): - Attachment: #2683 CellSurvAssay R package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/PickeringLab/CellSurvAssay > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:08:40): Unknown User (15:00:14): - Attachment: #2684 “CellSurvAssay” R package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/PickeringLab/CellSurvAssay > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-06-02

Unknown User (01:55:21): - Attachment: #2685 SpliceWiz R package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/alexchwong/SpliceWiz > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-06-03

Unknown User (08:14:30): Unknown User (09:10:33): Unknown User (09:24:22): Unknown User (09:26:53): Unknown User (09:33:18):

2022-06-06

Unknown User (05:19:09): - Attachment: #2686 iSEEhex > Tagging co-authors: @federicomarini, @LTLA, @csoneson > > > > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/iSEE/iSEEhex > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:58:01): Unknown User (11:54:29):

2022-06-07

Unknown User (14:49:13): - Attachment: #2687 EasyCellType > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rx-li/EasyCellType/tree/main > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:30:01): - Attachment: #2688 CITE-Viz > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: github.com/maxsonBraunLab/CITE-Viz > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:30:05): Unknown User (18:31:04): - Attachment: #2689 CITE-Viz > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/maxsonBraunLab/CITE-Viz > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:31:05): Unknown User (18:31:33): - Attachment: #2690 CITEViz > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/maxsonBraunLab/CITE-Viz > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:31:34): Unknown User (18:32:30): - Attachment: #2691 CITEViz > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/maxsonBraunLab/CITEViz > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:32:32):

2022-06-09

Unknown User (13:16:03): - Attachment: #2692 SRTsim > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository:https://github.com/jakezhusph/SRTsim > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:16:04):

2022-06-10

Unknown User (11:49:00): - Attachment: #2693 RedisParam > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mtmorgan/RedisParam > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-06-12

Unknown User (01:31:18): - Attachment: #2694 deepCE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mrbakhsh/deepCE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-06-13

Unknown User (10:25:32):

2022-06-15

Unknown User (07:42:58): Unknown User (07:46:35): Unknown User (14:34:16): - Attachment: #2695 ISLET > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/haoharryfeng/ISLET > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-06-16

Unknown User (17:12:16): - Attachment: #2696 FBCanalysis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/MrMaximumMax/FBCanalysis > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:12:18):

2022-06-17

Unknown User (17:55:20): - Attachment: #2697 FBCanalysis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/MrMaximumMax/FBCanalysis > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:55:22): Unknown User (17:56:06): - Attachment: #2698 FBCanalysis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/MrMaximumMax/FBCanalysis > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:56:07):

2022-06-20

Unknown User (05:58:45):

2022-06-21

Unknown User (10:59:57): - Attachment: #2699 signifinder > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CaluraLab/signifinder > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:59:58): Unknown User (11:08:33): - Attachment: #2700 signifinder > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CaluraLab/signifinder > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:08:37): Unknown User (11:18:27): - Attachment: #2701 signifinder > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CaluraLab/signifinder > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-06-22

Unknown User (15:22:12): - Attachment: #2702 FBCanalysis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/MrMaximumMax/FBCanalysis > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:22:14): Unknown User (15:43:56): - Attachment: #2703 FBCanalysis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/MrMaximumMax/FBCanalysis/blob/master/DESCRIPTION > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-06-27

Unknown User (02:36:42): - Attachment: #2704 Submission of the “phenomis” package for post-processing and univariate analysis of omics data > Dear Bioconductor team, > > > > > Please find below the GitHub link to the “phenomis” package that we would like to submit to Bioconductor. > > > > > The package provides methods for the post-processing (quality control, normalization), univariate hypothesis testing, clustering, and annotation of omics single or multiple datasets. It is mainly focused on metabolomics data but applications to proteomics and transcriptomics data are described in the vignette. > > > > > The package complements the “ropls” and “biosigner” Bioconductor packages, which focus on downstream multivariate analysis and feature selection. These 3 packages therefore enables to design comprehensive statistical and annotation workflows, as described in the vignette for single and multiple omics data sets. All of these 3 packages support the SummarizedExperiment and MultiAssayExperiment formats, but also the ExpressionSet and MultiDataSet formats. > > > > > We thank you in advance for reviewing the package. > > > > > Best Regards, > > > > > Etienne. > > > > > The remaining notes from the checks are commented below: > > > > > I. R CMD check: 1 note > > > > > 1. N checking for non-standard things in the check directory > Found the following files/directories: > ‘met_dataMatrix.tsv’ ‘met_sampleMetadata.tsv’ > ‘met_variableMetadata.tsv’ ‘metabo’ ‘pro_dataMatrix.tsv’ > ‘pro_sampleMetadata.tsv’ ‘pro_variableMetadata.tsv’ ‘prometis’ > > > > > This files/directories are generated in the examples of the “writing” method (note that the > \dontrun{} has been modified to \donttest{} according to the Bioconductor guidelines). > > > > > II. R CMD BiocCheck: 8 notes > > > > > 1. NOTE: Consider adding these automatically suggested biocViews: Sequencing, Coverage, KEGG > > > > > “BatchEffect” has been included as previously suggested. These remaining suggestions, however, are not relevant. > > > > > 2. NOTE: Avoid ‘cat’ and ‘print’ outside of ‘show’ methods > > > > > There is no call to ‘cat’. The very few calls to ‘print’ provide useful summaries which cannot be > provided by the ‘message’ function. > > > > > 3. NOTE: Avoid the use of ‘paste’ in condition signals > > > > > The very few uses of ‘paste’ provide the users with useful hints to address the raised issues. > > > > > 4. NOTE: Recommended function length <= 50 lines.There are 56 functions > 50 lines. > > > > > We did our best to shorten the function code. > > > > > 5. NOTE: Usage of dontrun{} / donttest{} found in man page examples.12% of man pages use one of these cases. > > > > > Annotating examples requiring to query the ChEBI database may take about 1 min and fail if the database is > unavailable for some reason. In addition, examples with the “writing” method have been flagged with ‘donttest’ > to avoid writing on the user file disk. > > > > > 6. NOTE: Consider shorter lines; 830 lines (7%) are > 80 characters long. > > > > > Again, we did our best to follow this recommendation. > > > > > 7. NOTE: Consider multiples of 4 spaces for line indents; 5006 lines (44%) are not. > > > > > I must admit that I am used to the 2 spaces which I find provides a clear view > of the indentations (and is the default with RStudio). Because I do not think that > there is an automated way to swith all the code to 4 spaces, I would prefer to stick > to this display in the package if possible > > > > > 8. NOTE: Cannot determine whether maintainer is subscribed to the Bioc-Devel mailing list (requires admin credentials). > > > > > I am member of the Bioc-Devel mailing list as a maintainer of the ropls and biosigner Bioconductor packages. > > > > > > > > > > > > > > > > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/odisce/phenomis > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (02:36:45): Unknown User (08:42:32): - Attachment: #2705 Submission of the new “phenomis” package for post-processing and univariate statistical analysis > Dear Bioconductor team, > > > > > Please find below the GitHub link to the “phenomis” package that we would like to submit to Bioconductor. > > > > > The package provides methods for the post-processing (quality control, normalization), univariate hypothesis testing, clustering, and annotation of omics single or multiple datasets. It is mainly focused on metabolomics data but applications to proteomics and transcriptomics data are described in the vignette. > > > > > The package complements the “ropls” and “biosigner” Bioconductor packages, which focus on downstream multivariate analysis and feature selection. These 3 packages therefore enables to design comprehensive statistical and annotation workflows, as described in the vignette for single and multiple omics data sets. All of these 3 packages support the SummarizedExperiment and MultiAssayExperiment formats, but also the ExpressionSet and MultiDataSet formats. > > > > > We thank you in advance for reviewing the package. > > > > > Best Regards, > > > > > Etienne. > > > > > The remaining notes from the checks are commented below: > > > > > I. R CMD check: 1 note > > > > > 1. N checking for non-standard things in the check directory > Found the following files/directories: > ‘met_dataMatrix.tsv’ ‘met_sampleMetadata.tsv’ > ‘met_variableMetadata.tsv’ ‘metabo’ ‘pro_dataMatrix.tsv’ > ‘pro_sampleMetadata.tsv’ ‘pro_variableMetadata.tsv’ ‘prometis’ > > > > > This files/directories are generated in the examples of the “writing” method (note that the > \dontrun{} has been modified to \donttest{} according to the Bioconductor guidelines). > > > > > II. R CMD BiocCheck: 8 notes > > > > > 1. NOTE: Consider adding these automatically suggested biocViews: Sequencing, Coverage, KEGG > > > > > “BatchEffect” has been included as previously suggested. These remaining suggestions, however, are not relevant. > > > > > 2. NOTE: Avoid ‘cat’ and ‘print’ outside of ‘show’ methods > > > > > There is no call to ‘cat’. The very few calls to ‘print’ provide useful summaries which cannot be > provided by the ‘message’ function. > > > > > 3. NOTE: Avoid the use of ‘paste’ in condition signals > > > > > The very few uses of ‘paste’ provide the users with useful hints to address the raised issues. > > > > > 4. NOTE: Recommended function length <= 50 lines.There are 56 functions > 50 lines. > > > > > We did our best to shorten the function code. > > > > > 5. NOTE: Usage of dontrun{} / donttest{} found in man page examples.12% of man pages use one of these cases. > > > > > Annotating examples requiring to query the ChEBI database may take about 1 min and fail if the database is > unavailable for some reason. In addition, examples with the “writing” method have been flagged with ‘donttest’ > to avoid writing on the user file disk. > > > > > 6. NOTE: Consider shorter lines; 830 lines (7%) are > 80 characters long. > > > > > Again, we did our best to follow this recommendation. > > > > > 7. NOTE: Consider multiples of 4 spaces for line indents; 5006 lines (44%) are not. > > > > > I must admit that I am used to the 2 spaces which I find provides a clear view > of the indentations (and is the default with RStudio). Because I do not think that > there is an automated way to swith all the code to 4 spaces, I would prefer to stick > to this display in the package if possible > > > > > 8. NOTE: Cannot determine whether maintainer is subscribed to the Bioc-Devel mailing list (requires admin credentials). > > > > > I am member of the Bioc-Devel mailing list as a maintainer of the ropls and biosigner Bioconductor packages. > > > > > > > > > > > > > > > > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/odisce/phenomis > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:42:34): Unknown User (09:21:16): - Attachment: #2706 Submission of the new “phenomis” package for postprocessing and univariate analysis of omics data > Dear Bioconductor team, > > > > > Please find below the GitHub link to the “phenomis” package that we would like to submit to Bioconductor. > > > > > The package provides methods for the post-processing (quality control, normalization), univariate hypothesis testing, clustering, and annotation of omics single or multiple datasets. It is mainly focused on metabolomics data but applications to proteomics and transcriptomics data are described in the vignette. > > > > > The package complements the “ropls” and “biosigner” Bioconductor packages, which focus on downstream multivariate analysis and feature selection. These 3 packages therefore enables to design comprehensive statistical and annotation workflows, as described in the vignette for single and multiple omics data sets. All of these 3 packages support the SummarizedExperiment and MultiAssayExperiment formats, but also the ExpressionSet and MultiDataSet formats. > > > > > We thank you in advance for reviewing the package. > > > > > Best Regards, > > > > > Etienne. > > > > > The remaining notes from the checks are commented below: > > > > > I. R CMD check: 1 note > > > > > 1. N checking for non-standard things in the check directory > Found the following files/directories: > ‘met_dataMatrix.tsv’ ‘met_sampleMetadata.tsv’ > ‘met_variableMetadata.tsv’ ‘metabo’ ‘pro_dataMatrix.tsv’ > ‘pro_sampleMetadata.tsv’ ‘pro_variableMetadata.tsv’ ‘prometis’ > > > > > This files/directories are generated in the examples of the “writing” method (note that the > \dontrun{} has been modified to \donttest{} according to the Bioconductor guidelines). > > > > > II. R CMD BiocCheck: 8 notes > > > > > 1. NOTE: Consider adding these automatically suggested biocViews: Sequencing, Coverage, KEGG > > > > > “BatchEffect” has been included as previously suggested. These remaining suggestions, however, are not relevant. > > > > > 2. NOTE: Avoid ‘cat’ and ‘print’ outside of ‘show’ methods > > > > > There is no call to ‘cat’. The very few calls to ‘print’ provide useful summaries which cannot be > provided by the ‘message’ function. > > > > > 3. NOTE: Avoid the use of ‘paste’ in condition signals > > > > > The very few uses of ‘paste’ provide the users with useful hints to address the raised issues. > > > > > 4. NOTE: Recommended function length <= 50 lines.There are 56 functions > 50 lines. > > > > > We did our best to shorten the function code. > > > > > 5. NOTE: Usage of dontrun{} / donttest{} found in man page examples.12% of man pages use one of these cases. > > > > > Annotating examples requiring to query the ChEBI database may take about 1 min and fail if the database is > unavailable for some reason. In addition, examples with the “writing” method have been flagged with ‘donttest’ > to avoid writing on the user file disk. > > > > > 6. NOTE: Consider shorter lines; 830 lines (7%) are > 80 characters long. > > > > > Again, we did our best to follow this recommendation. > > > > > 7. NOTE: Consider multiples of 4 spaces for line indents; 5006 lines (44%) are not. > > > > > I must admit that I am used to the 2 spaces which I find provides a clear view > of the indentations (and is the default with RStudio). Because I do not think that > there is an automated way to swith all the code to 4 spaces, I would prefer to stick > to this display in the package if possible > > > > > 8. NOTE: Cannot determine whether maintainer is subscribed to the Bioc-Devel mailing list (requires admin credentials). > > > > > I am member of the Bioc-Devel mailing list as a maintainer of the ropls and biosigner Bioconductor packages. > > > > > > > > > > > > > > > > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/odisce/phenomis > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:33:59): - Attachment: #2707 UniProtKeywords > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jokergoo/UniProtKeywords > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-06-28

Unknown User (08:20:49): Unknown User (08:27:49): Unknown User (08:27:49): Unknown User (08:27:51): Unknown User (08:27:52): Unknown User (08:27:54): Unknown User (08:27:56):

2022-06-30

Unknown User (07:24:25):

2022-07-05

Unknown User (08:06:53): Unknown User (08:55:07):

2022-07-06

Unknown User (03:03:05): - Attachment: #2708 cardelino > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/single-cell-genetics/cardelino > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (03:03:07): Unknown User (03:10:26): - Attachment: #2709 cardelino > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/single-cell-genetics/cardelino > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (03:10:28): Unknown User (07:16:31): Unknown User (07:37:58): Unknown User (14:27:52): Unknown User (14:27:53): Unknown User (14:27:54): Unknown User (14:27:56): Unknown User (14:27:57): Unknown User (14:27:58): Unknown User (21:24:10): - Attachment: #2710 cardelino > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/single-cell-genetics/cardelino > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-07-07

Unknown User (22:05:10): - Attachment: #2711 R package InteRD to Bioconductor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/chencxxy/InteRD > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:05:11): Unknown User (22:07:05): - Attachment: #2712 R package to Bioconductor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/chencxxy28/InteRD > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:07:06):

2022-07-11

Unknown User (02:45:16): - Attachment: #2713 LipidSigR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/TMSWCChenglab/LipidSigR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (02:45:18): Unknown User (07:38:43):

2022-07-12

Unknown User (08:21:23): - Attachment: #2714 rifiComparative > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CyanolabFreiburg/rifiComparative/tree/main > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:21:25):

2022-07-13

Unknown User (10:29:46):

2022-07-15

Unknown User (00:09:43): - Attachment: #2715 ssde > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/hd2326/ssde > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (00:09:46): Unknown User (00:21:39): - Attachment: #2716 ssde > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/hd2326/ssde > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (03:32:49): Unknown User (03:32:58): Unknown User (03:45:20): - Attachment: #2717 https://github.com/CyanolabFreiburg/rifiComparative > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (03:45:21): Unknown User (03:57:15): - Attachment: #2718 rifiComparative > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CyanolabFreiburg/rifiComparative > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:25:57): - Attachment: #2719 SFEData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/pachterlab/SFEData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-07-17

Unknown User (12:28:57): - Attachment: #2720 MsExperiment submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/RforMassSpectrometry/MsExperiment/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:19:27): - Attachment: #2721 smoothLRC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/alexanderjwhite/smoothLRC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-07-18

Unknown User (07:42:39): Unknown User (07:42:40): Unknown User (07:42:41): Unknown User (07:42:43): Unknown User (08:28:16): - Attachment: #2722 New package vsclust > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/veitveit/vsclust > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:28:22): Unknown User (08:31:04): - Attachment: #2723 vsclust > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/veitveit/vsclust > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:31:08): Unknown User (08:35:26): - Attachment: #2724 vsclust > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/veitveit/vsclust > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-07-19

Unknown User (16:52:19): - Attachment: #2725 MerfishData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ccb-hms/MerfishData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x ] The ‘devel’ branch for new packages and features. > • [ x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (19:37:31): - Attachment: #2726 demuxmix > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/huklein/demuxmix > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-07-20

Unknown User (15:41:55): - Attachment: #2727 VDJdive > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/kstreet13/VDJdive > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:41:56): Unknown User (15:49:12): - Attachment: #2728 VDJdive > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/kstreet13/VDJdive > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-07-21

Unknown User (03:53:37): - Attachment: #2729 BASiCStan > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Alanocallaghan/BASiCStan > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-07-23

Unknown User (07:33:31): Unknown User (07:33:54):

2022-07-26

Unknown User (10:26:42): Unknown User (12:41:05): - Attachment: #2730 crisprDesignData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Jfortin1/crisprDesignData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:41:07):

2022-07-27

Unknown User (10:20:16): - Attachment: #2731 epistasisGA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mnodzenski/epistasisGA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:44:46): Unknown User (15:44:48): Unknown User (15:44:49):

2022-07-28

Unknown User (17:27:10): - Attachment: #2732 rd4 initial submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/fulcrumgenomics/rd4 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-07-31

Unknown User (02:05:24): - Attachment: #2733 Submit the HDO.db package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/YuLab-SMU/HDO.db > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (02:05:26): Unknown User (10:24:13): - Attachment: #2734 Submit HDO.db package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/YuLab-SMU/HDO.db > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-08-01

Unknown User (12:05:02): - Attachment: #2735 crisprVerse > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/crisprVerse/crisprVerse > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:08:27): - Attachment: #2736 crisprViz > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Jfortin1/crisprViz > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-08-02

Unknown User (10:23:17): Unknown User (11:43:03): - Attachment: #2737 iDA submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/reesyxan/iDA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:30:25): - Attachment: #2738 CITEViz > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/maxsonBraunLab/CITEViz > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-08-03

Unknown User (04:05:29): - Attachment: #2739 Genefusiondiscover > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CTrierMaansson/Genefusiondiscover > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-08-08

Unknown User (07:39:13): - Attachment: #2740 New submission regioneReloaded package to Bioconductor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/RMalinverni/regioneReloaded > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:39:15): Unknown User (07:49:05): - Attachment: #2741 regioneReloaded package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/RMalinverni/regioneReloaded > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:17:35): Unknown User (11:17:37): Unknown User (19:36:20): Unknown User (19:37:21): Unknown User (23:09:44): - Attachment: #2742 CircSeqAlignTk > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jsun/CircSeqAlignTk > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-08-09

Unknown User (02:49:53): - Attachment: #2743 IntoOMICS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/anna-pacinkova/intomics_package > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (02:49:55): Unknown User (03:00:21): - Attachment: #2744 IntOMICS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/anna-pacinkova/IntOMICS > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-08-11

Unknown User (13:07:03): - Attachment: #2745 scifer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rodrigarc/scifer > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:37:15): Unknown User (18:37:32): - Attachment: #2746 CITEViz > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/maxsonBraunLab/CITEViz > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:37:34): Unknown User (18:38:42):

2022-08-12

Unknown User (03:22:13): - Attachment: #2747 ggtreeDendro > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/YuLab-SMU/ggtreeDendro > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (03:22:15): Unknown User (04:04:27): - Attachment: #2748 ggtreeDendro > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/YuLab-SMU/ggtreeDendro > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:08:50): Unknown User (11:08:51):

2022-08-15

Unknown User (08:21:53):

2022-08-16

Unknown User (06:34:46): - Attachment: #2749 iSEEhub > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/iSEE/iSEEhub/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:31:42): - Attachment: #2750 FuseSOM > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ecool50/FuseSOM > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:31:44): Unknown User (20:05:47): - Attachment: #2751 FuseSOM > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ecool50/FuseSOM > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-08-17

Unknown User (12:48:26): - Attachment: #2752 genomicRegionsFromGeneSymbols > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/davidechicco/genomicRegionsFromGeneSymbols > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-08-18

Unknown User (13:29:39): Unknown User (13:29:40): Unknown User (13:29:41): Unknown User (13:29:43): Unknown User (13:29:44): Unknown User (19:49:06):

2022-08-19

Unknown User (02:55:24): Unknown User (16:35:19):

2022-08-21

Unknown User (23:12:56): Unknown User (23:14:34):

2022-08-24

Unknown User (19:05:24): - Attachment: #2753 TENxIO > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/waldronlab/TENxIO > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-08-26

Unknown User (02:58:34): - Attachment: #2754 magrene > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/almeidasilvaf/magrene > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-08-29

Unknown User (01:14:54): Unknown User (07:59:27): Unknown User (10:17:26): - Attachment: #2755 HiContactsData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/js2264/HiContactsData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:17:30): Unknown User (10:21:52): - Attachment: #2756 HiContactsData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/js2264/HiContactsData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:21:56): Unknown User (10:34:03): - Attachment: #2757 HiContactsData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/js2264/HiContactsData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-08-30

Unknown User (15:57:23): - Attachment: #2758 EDIRquery > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lauravongoc/EDIRquery > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-08-31

Unknown User (12:07:51): Unknown User (12:08:02): Unknown User (14:11:04): - Attachment: #2759 DNAfusion > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://https://github.com/CTrierMaansson/DNAfusion > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-09-02

Unknown User (10:41:03):

2022-09-04

Unknown User (16:40:17): - Attachment: #2760 https://github.com/yuabrahamliu/scDeconv > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:40:18): Unknown User (16:46:01): - Attachment: #2761 scDeconv > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yuabrahamliu/scDeconv > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:46:03): Unknown User (16:58:51): - Attachment: #2762 scDeconv > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yuabrahamliu/scDeconv > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:58:54):

2022-09-09

Unknown User (07:19:38): Unknown User (07:19:39): Unknown User (07:19:40): Unknown User (07:19:41): Unknown User (07:19:43): Unknown User (07:19:44): Unknown User (19:41:38): - Attachment: #2763 MetaPhOR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/emilyise/MetaPhOR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (19:41:40): Unknown User (19:45:38): - Attachment: #2764 MetaPhOR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yemilyise/MetaPhOR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (19:45:40): Unknown User (19:46:20): - Attachment: #2765 MetaPhOR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/emilyise/MetaPhOR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-09-13

Unknown User (16:57:57): - Attachment: #2766 cytofQC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jillbo1000/cytofQC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-09-14

Unknown User (07:00:37): - Attachment: #2767 NetActivityData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ X] The ‘devel’ branch for new packages and features. > • [ X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:00:39): Unknown User (07:02:09): - Attachment: #2768 NetActivityData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yocra3/NetActivityData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:02:12): Unknown User (07:10:28): - Attachment: #2769 NetActivityData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yocra3/NetActivityData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-09-15

Unknown User (07:34:50):

2022-09-16

Unknown User (04:40:33): - Attachment: #2770 simpleSeg > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/simpleSeg > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:40:35): Unknown User (05:18:15): - Attachment: #2771 simpleSeg > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/simpleSeg > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:18:18): Unknown User (06:23:22): - Attachment: #2772 simpleSeg > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/simpleSeg > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (06:23:25): Unknown User (06:43:35): - Attachment: #2773 simpleSeg > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/simpleSeg > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (06:43:37): Unknown User (06:46:41): - Attachment: #2774 simpleSeg > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/simpleSeg > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-09-20

Unknown User (04:03:47): - Attachment: #2775 MsQuality > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tnaake/MsQuality > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:03:50): Unknown User (04:30:28): - Attachment: #2776 MsQuality > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tnaake/MsQuality > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:42:43): - Attachment: #2777 BioMartGOGeneSets > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jokergoo/BioMartGOGeneSets > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-09-23

Unknown User (02:42:37): - Attachment: #2778 speckle package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/phipsonlab/speckle > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:01:07): - Attachment: #2779 scBubbletree > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/snaketron/scBubbletree > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:01:09): Unknown User (09:06:29): - Attachment: #2780 BioNAR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lptolik/BioNAR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:07:54): - Attachment: #2781 scBubbletree > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/snaketron/scBubbletree > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-09-24

Unknown User (15:12:44):

2022-09-26

Unknown User (07:18:09): Unknown User (09:18:03): Unknown User (09:18:05): Unknown User (09:18:06): Unknown User (09:18:07): Unknown User (09:18:09): Unknown User (09:18:11):

2022-09-27

Unknown User (09:13:00): - Attachment: #2782 MSstatsShiny > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Vitek-Lab/MSstatsShiny > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:13:03): Unknown User (09:22:20): - Attachment: #2783 MSstatsShiny > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Vitek-Lab/MSstatsShiny > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:03:47): - Attachment: #2784 Totem > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/elolab/Totem > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:03:51): Unknown User (12:09:18): - Attachment: #2785 Totem > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/elolab/Totem > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:34:43): - Attachment: #2786 DunedinPACE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/danbelsky/DunedinPACE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:34:45): Unknown User (17:44:00): - Attachment: #2787 DunedinPACE submission to bioconductor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/danbelsky/DunedinPACE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:44:02): Unknown User (17:47:12): - Attachment: #2788 DunedinPACE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/danbelsky/DunedinPACE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:47:14): Unknown User (18:01:43): - Attachment: #2789 DunedinPACE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/danbelsky/DunedinPACE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-09-29

Unknown User (11:46:58): - Attachment: #2790 seqArchRplus > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/snikumbh/seqArchRplus > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-10-03

Unknown User (14:53:20): Unknown User (15:19:29): - Attachment: #2791 MicrobiomeBenchmarkData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/waldronlab/MicrobiomeBenchmarkData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (19:06:10): - Attachment: #2792 RBioFormats > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/aoles/RBioFormats > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (19:06:12): Unknown User (19:33:36): - Attachment: #2793 RBioFormats > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/aoles/RBioFormats > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-10-04

Unknown User (06:14:15): - Attachment: #2794 microSTASIS > • Repository: https://github.com/BiotechPedro/microSTASIS > > • Additional important correspondence: The former version of the package was submitted to CRAN one year ago. Therefore, there is an error regarding the package is in CRAN. They (CRAN@R-project.org|CRAN@R-project.org) replied the following to me: > > > > > > “The way this is usually done is that you get your package added to BioC devel and only this gets released we archive the package from CRAN”. > > > > > So, I will immediately remind it to them once the package is released. > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor [Package Submission][2] > instructions. My package is consistent with the Bioconductor > [Package Guidelines][1]. > > • [x] I understand Bioconductor [Package Naming Policy][9] and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the [support site][3] for issues that users may > have, subscribing to the [bioc-devel][4] mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the [Bioconductor code of conduct][7] and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using [Git][5] > (optionally [via GitHub][6]).

Unknown User (06:14:17): Unknown User (06:50:18): - Attachment: #2795 microSTASIS > • Repository: https://github.com/BiotechPedro/microSTASIS > > • Additional important correspondence: The former version of the package was > submitted to CRAN one year ago. Therefore, there is an error regarding the > package is in CRAN. (mailto:CRAN@R-project.org|They) replied the > following to me the following, so I will immediately remind it to them once the > package is released. > > > > > > > “The way this is usually done is that you get your package added to BioC devel and only this gets released we archive the package from CRAN”. > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:35:35): Unknown User (19:15:58): - Attachment: #2796 metabinR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/gkanogiannis/metabinR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-10-05

Unknown User (03:23:27): - Attachment: #2797 ASCETIC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/danro9685/ASCETIC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (03:25:55): - Attachment: #2798 SparseSignaturesPlus > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/danro9685/SparseSignaturesPlus > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:54:54): Unknown User (12:08:13): Unknown User (17:08:57): - Attachment: #2799 InSituType > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Nanostring-Biostats/InSituType > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-10-06

Unknown User (08:17:02): - Attachment: #2800 doubletrouble > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/almeidasilvaf/doubletrouble > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:20:14): - Attachment: #2801 WeberDivechaLCdata > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lmweber/WeberDivechaLCdata > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:15:29): - Attachment: #2802 SGC: A semi-supervised pipeline for gene clustering using self-training approach in gene co-expression networks > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/na396/SGC > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:15:32): Unknown User (16:56:48): - Attachment: #2803 SGC: A semi-supervised pipeline for gene clustering using self-training approach in gene co-expression networks > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/na396/SGC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ]x I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:56:51): Unknown User (16:58:01): - Attachment: #2804 curatedPCaData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Syksy/curatedPCaData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:58:05): Unknown User (17:02:41): - Attachment: #2805 SGC: A semi-supervised pipeline for gene clustering using self-training approach in gene co-expression networks > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/na396/SGC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ]x I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:02:43): Unknown User (17:03:32): - Attachment: #2806 SGC: A semi-supervised pipeline for gene clustering using self-training approach in gene co-expression networks. > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/na396/SGC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:03:35): Unknown User (19:23:49): - Attachment: #2807 BiocFHIR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/vjcitn/BiocFHIR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (19:23:51): Unknown User (19:25:02): Unknown User (22:17:47): - Attachment: #2808 betAS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/marianaferreira/betAS > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:17:49): Unknown User (22:32:52): - Attachment: #2809 betAS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/marianaferreira/betAS > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:32:55): Unknown User (22:41:23): - Attachment: #2810 betAS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/marianaferreira/betAS > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-10-07

Unknown User (03:23:03): - Attachment: #2811 tfhunter > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/almeidasilvaf/tfhunter > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (03:42:20): - Attachment: #2812 scFeatures > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/scFeatures > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (03:42:22): Unknown User (03:53:52): - Attachment: #2813 scFeatures > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/scFeatures > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (03:53:56): Unknown User (04:03:56): - Attachment: #2814 scFeatures > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/scFeatures > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:03:58): Unknown User (04:06:17): - Attachment: #2815 scFeatures > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/scFeatures > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:17:54): - Attachment: #2816 Statial > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/Statial > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:17:56): Unknown User (04:28:49): - Attachment: #2817 Statial > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/Statial > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:28:52): Unknown User (04:47:04): - Attachment: #2818 Statial > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/Statial > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:49:20): Unknown User (10:47:44): - Attachment: #2819 SGC : A semi-supervised pipeline for gene clustering. > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/na396/SGC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:47:46): Unknown User (10:50:24): - Attachment: #2820 SGC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/na396/SGC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:50:26): Unknown User (11:19:32): - Attachment: #2821 SGC: A semi-supervised pipeline for gene clustering using self-training approach in gene co-expression networks > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/na396/SGC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:19:35): Unknown User (11:48:56): - Attachment: #2822 SGC: A semi-supervised pipeline for gene clustering using self-training approach in gene co-expression networks > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/na396/SGC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:48:58): Unknown User (12:06:26): - Attachment: #2823 survClust > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/arorarshi/survClust/tree/dev > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:06:28): Unknown User (12:11:11): - Attachment: #2824 SGC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/na396/SGC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:11:13): Unknown User (12:16:33): - Attachment: #2825 survClust > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/arorarshi/survClust > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:16:35): Unknown User (12:18:05): - Attachment: #2826 SGC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/na396/SGC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:18:07): Unknown User (12:24:18): - Attachment: #2827 SGC-Pipeline > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/na396/SGC-Pipeline > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:24:20): Unknown User (12:32:13): - Attachment: #2828 SGC-Pipeline > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/na396/SGC-Pipeline > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:35:53): - Attachment: #2829 survClust > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/arorarshi/survClust > • > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:17:22): - Attachment: #2830 AnVILWorkflow > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/shbrief/AnVILWorkflow > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:17:24): Unknown User (22:20:56): - Attachment: #2831 AnVILWorkflow > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/shbrief/AnVILWorkflow > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:20:57): Unknown User (22:23:12): - Attachment: #2832 AnVILWorkflow > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/shbrief/AnVILWorkflow > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-10-08

Unknown User (06:57:43): - Attachment: #2833 VSOLassoBag > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/likelet/VSOLassoBag > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (06:57:46): Unknown User (07:43:55): - Attachment: #2834 VSOLassoBag > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/likelet/VSOLassoBag > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-10-11

Unknown User (08:04:03): Unknown User (08:05:08): - Attachment: #2835 planttfhunter > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/almeidasilvaf/planttfhunter > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:02:57): Unknown User (12:03:31): Unknown User (12:03:33): Unknown User (12:03:35): Unknown User (12:03:36): Unknown User (12:03:38): Unknown User (12:05:23): Unknown User (12:10:26): - Attachment: #2836 BiocFHIR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/vjcitn/BiocFHIR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:47:29): Unknown User (14:48:23):

2022-10-13

Unknown User (07:20:14): - Attachment: #2837 CytoPipeline package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/UCLouvain-CBIO/CytoPipeline > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:20:17): Unknown User (08:40:41): - Attachment: #2838 Submit CytoPipeline package (2nd attempt) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/UCLouvain-CBIO/CytoPipeline > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:12:30): - Attachment: #2839 CITEViz-ExperimentHub > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/maxsonBraunLab/CITEVizTestData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-10-14

Unknown User (07:38:14): Unknown User (11:04:17): - Attachment: #2840 SGCP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/na396/SGCP > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:05:29):

2022-10-17

Unknown User (08:14:54): Unknown User (08:14:56): Unknown User (11:02:44): Unknown User (11:40:29): - Attachment: #2841 RESOLVE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/danro9685/RESOLVE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:50:12): - Attachment: #2842 mnmer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/labinfo-lncc/mnmer.git > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:50:13): Unknown User (16:55:32): - Attachment: #2843 mnmer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/labinfo-lncc/mnmer > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-10-18

Unknown User (09:10:45): Unknown User (09:10:46): Unknown User (09:10:47): Unknown User (09:10:49):

2022-10-21

Unknown User (07:21:18): Unknown User (07:21:19): Unknown User (07:21:20):

2022-10-25

Unknown User (07:36:04): Unknown User (07:36:08): Unknown User (07:36:10): Unknown User (07:36:12): Unknown User (07:36:13): Unknown User (07:36:15):

2022-10-26

Unknown User (07:43:12): Unknown User (07:43:48): Unknown User (07:48:45): Unknown User (07:53:07): Unknown User (08:01:04): Unknown User (08:01:45): Unknown User (08:02:14): Unknown User (08:34:05): Unknown User (08:34:07): Unknown User (08:34:09): Unknown User (08:34:10): Unknown User (08:34:13): Unknown User (08:34:16): Unknown User (08:34:18):

2022-10-28

Unknown User (11:50:09): Unknown User (11:50:11): Unknown User (11:50:13): Unknown User (11:50:14): Unknown User (17:12:46): - Attachment: #2844 MetaScope > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/compbiomed/MetaScope > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-10-29

Unknown User (10:57:03): - Attachment: #2845 ceRNAR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ywhsiao/ceRNAR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:57:05): Unknown User (11:08:56): - Attachment: #2846 ceRNAR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ywhsiao/ceRNA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x ] The ‘devel’ branch for new packages and features. > • [ x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:08:58): Unknown User (11:09:53): - Attachment: #2847 ceRNAR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ywhsiao/ceRNAR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x ] The ‘devel’ branch for new packages and features. > • [ x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-10-31

Unknown User (14:45:01): - Attachment: #2848 SVMDO > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/robogeno/SVMDO > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-11-02

Unknown User (05:13:36): Unknown User (05:14:11): Unknown User (10:50:54): - Attachment: #2849 CaDrA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/montilab/CaDrA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:50:57): Unknown User (10:58:15): - Attachment: #2850 CaDrA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/montilab/CaDrA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-11-03

Unknown User (17:16:12): - Attachment: #2851 acorn > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/TNTurnerLab/acorn > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:16:14): Unknown User (17:24:16): - Attachment: #2852 acorn > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/TNTurnerLab/acorn > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:24:18): Unknown User (17:33:48): - Attachment: #2853 acorn > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/TNTurnerLab/acorn > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-11-08

Unknown User (13:10:39): - Attachment: #2854 PloidyPeaks > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/margothenry/PloidyPeaks > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:10:42): Unknown User (13:45:57): - Attachment: #2855 ploidyPeaks > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/margothenry/PloidyPeaks > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-11-09

Unknown User (09:11:54): Unknown User (09:11:56): Unknown User (09:11:58): Unknown User (17:29:18): - Attachment: #2856 edgeCounter > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yeyuan98/edgeCounter > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:50:15): - Attachment: #2857 cfdnakit package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Pitithat-pu/cfdnakit > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-11-10

Unknown User (15:05:02): Unknown User (15:19:12):

2022-11-16

Unknown User (13:55:17): Unknown User (13:55:21):

2022-11-23

Unknown User (04:50:53): - Attachment: #2859 MsBackendSql package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/RforMassSpectrometry/MsBackendSql > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-11-26

Unknown User (12:39:01): - Attachment: #2860 clevRvis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/sandmanns/clevRvis > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-11-28

Unknown User (19:39:33): - Attachment: #2861 partCNV > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rx-li/partCNV > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (19:48:13):

2022-11-30

Unknown User (04:15:22): - Attachment: #2862 GeoTcgaData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/YuLab-SMU/GeoTcgaData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:23:29): - Attachment: #2863 ChromENVEE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ManonCoulee/ChromENVEE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:23:32): Unknown User (05:36:46): - Attachment: #2864 ChromENVEE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ManonCoulee/ChromENVEE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-12-01

Unknown User (07:51:15): Unknown User (07:51:16):

2022-12-05

Unknown User (16:55:35): - Attachment: #2865 ReUseData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rworkflow/ReUseData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:55:37): Unknown User (17:01:11): - Attachment: #2866 ReUseData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rworkflow/ReUseData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:01:14): Unknown User (17:42:03): - Attachment: #2867 ReUseData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rworkflow/ReUseData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:42:05): Unknown User (17:57:37): - Attachment: #2868 ReUseData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rworkflow/ReUseData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-12-09

Unknown User (12:36:42): - Attachment: #2869 HicAggR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CuvierLab/HicAggR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-12-10

Unknown User (23:25:09):

2022-12-12

Unknown User (03:46:04): - Attachment: #2870 DCATS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/holab-hku/DCATS > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (03:46:32): Unknown User (09:17:51): - Attachment: #2871 BG2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/marf-at-vt/BG2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:18:40):

2022-12-13

Unknown User (06:58:21): Unknown User (13:33:40): Unknown User (13:34:51): Unknown User (20:49:49): - Attachment: #2872 INTACT > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jokamoto97/INTACT > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:50:18):

2022-12-14

Unknown User (06:58:57): Unknown User (06:59:38): Unknown User (07:01:29): Unknown User (07:03:06):

2022-12-15

Unknown User (10:35:35): - Attachment: #2873 BiocHail > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/vjcitn/BiocHail > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:35:37): Unknown User (10:38:26): - Attachment: #2874 BiocHail > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/vjcitn/BiocHail > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:38:28): Unknown User (10:41:14): - Attachment: #2875 BiocHail > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:41:16): Unknown User (10:42:47): - Attachment: #2876 BiocHail > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/vjcitn/BiocHail > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:42:50): Unknown User (14:00:35): - Attachment: #2877 MarZIC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/quranwu/MarZIC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-12-16

Unknown User (07:14:14): Unknown User (07:15:22): Unknown User (07:16:22): Unknown User (07:17:41):

2022-12-19

Unknown User (09:59:52): - Attachment: #2878 HiCExperiment > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/js2264/HiCExperiment > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:59:54): Unknown User (10:07:43): - Attachment: #2879 HiCExperiment > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/js2264/HiCExperiment > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:12:32): Unknown User (12:12:33): Unknown User (12:12:35):

2022-12-23

Unknown User (10:39:47): - Attachment: #2880 New package submission, HERON, for analyzing peptide binding array data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Ong-Research/HERON > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:28:12): - Attachment: #2881 scRNAseqApp > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jianhong/scRNAseqApp > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:28:14): Unknown User (12:50:45): - Attachment: #2882 scRNAseqApp > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jianhong/scRNAseqApp > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-12-28

Unknown User (13:32:16): - Attachment: #2883 TimeSeriesAnalysis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Ylefol/TimeSeriesAnalysis > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2022-12-29

Unknown User (14:51:25): - Attachment: #2884 SVMDO > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/robogeno/SVMDO > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:51:28):

2022-12-30

Unknown User (14:29:08):

2023-01-03

Unknown User (07:08:35): Unknown User (12:47:43): Unknown User (12:47:44): Unknown User (12:47:46): Unknown User (21:51:37): - Attachment: #2885 DiffCircaPipeline > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/DiffCircaPipeline/DiffCircaPipeline > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (21:51:40): Unknown User (22:33:22): - Attachment: #2886 DiffCircaPipeline > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/DiffCircaPipeline/DiffCircaPipeline > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-01-04

Unknown User (11:18:10): - Attachment: #2887 MsDataHub submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/RforMassSpectrometry/MsDataHub > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-01-05

Unknown User (20:24:21): - Attachment: #2888 OutSplice > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/GuoLabUCSD/OutSplice > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-01-06

Unknown User (12:44:12): Unknown User (14:52:40): - Attachment: #2889 OutSplice > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/GuoLabUCSD/OutSplice > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:52:42): Unknown User (14:53:42):

2023-01-09

Unknown User (04:26:19): - Attachment: #2890 SiPSiC > • Repository: https://github.com/DanielDavis12/SiPSiC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:26:21): Unknown User (04:33:07): - Attachment: #2891 SiPSiC > Repository: https://github.com/DanielDavis12/SiPSiC > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:23:23): Unknown User (07:23:28): Unknown User (22:30:41): - Attachment: #2892 alabaster.schemas > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ArtifactDB/alabaster.schemas > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:30:43): Unknown User (22:49:57): - Attachment: #2893 alabaster.schemas > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ArtifactDB/alabaster.schemas > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:49:59): Unknown User (22:52:29): - Attachment: #2894 alabaster.schemas > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ArtifactDB/alabaster.schemas > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-01-11

Unknown User (19:28:27):

2023-01-13

Unknown User (21:23:34): - Attachment: #2895 magpieData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/dxd429/magpieData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (21:23:36): Unknown User (21:28:00): - Attachment: #2896 magpieData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/dxd429/magpieData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (21:28:02): Unknown User (21:36:50): - Attachment: #2897 magpieData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/dxd429/magpieData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (21:36:53): Unknown User (22:14:05): - Attachment: #2898 magpie > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/dxd429/magpie > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-01-15

Unknown User (20:59:55): - Attachment: #2899 Please add package mbQTL > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Mercedeh66/mbQTL > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-01-17

Unknown User (22:00:04):

2023-01-18

Unknown User (21:19:29):

2023-01-20

Unknown User (07:45:54): Unknown User (07:45:56): Unknown User (11:14:18): - Attachment: #2900 ClusterFoldSimilarity > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/OscarGVelasco/ClusterFoldSimilarity > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:30:35): - Attachment: #2901 scMultiome > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/xiaosaiyao/scMultiome > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:42:37): - Attachment: #2902 scDesign3 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SONGDONGYUAN1994/scDesign3 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:42:39): Unknown User (18:01:14): - Attachment: #2903 scDesign3 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SONGDONGYUAN1994/scDesign3 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-01-22

Unknown User (20:23:10): - Attachment: #2904 TDbasedUFE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tagtag/TDbasedUFE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:23:12): Unknown User (22:45:56): - Attachment: #2905 TDbasedUFE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tagtag/TDbasedUFE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:45:59): Unknown User (23:02:16): - Attachment: #2906 TDbasedUFE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tagtag/TDbasedUFE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-01-23

Unknown User (09:00:28): - Attachment: #2907 shiny.gosling > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Appsilon/shiny.gosling > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-01-24

Unknown User (01:34:03): - Attachment: #2908 itol.toolkit > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/TongZhou2017/itol.toolkit > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (01:34:07): Unknown User (01:39:40): - Attachment: #2909 itol.toolkit > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/TongZhou2017/itol.toolkit > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (01:39:42): Unknown User (01:45:38): - Attachment: #2910 itol.toolkit > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/TongZhou2017/itol.toolkit > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (01:45:41):

2023-01-25

Unknown User (18:18:20): - Attachment: #2911 TDbasedUFE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tagtag/TDbasedUFE > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:18:23): Unknown User (18:20:12): - Attachment: #2912 TDbasedUFE revision 1 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tagtag/TDbasedUFE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:20:15):

2023-01-26

Unknown User (11:40:34): Unknown User (11:41:52):

2023-01-27

Unknown User (14:40:28): - Attachment: #2913 nipalsMCIA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Muunraker/nipalsMCIA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:40:30): Unknown User (14:54:12): - Attachment: #2914 nipalsMCIA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Muunraker/nipalsMCIA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-01-30

Unknown User (07:50:50): Unknown User (07:50:52): Unknown User (07:50:54):

2023-01-31

Unknown User (11:14:50): Unknown User (11:15:32):

2023-02-01

Unknown User (17:32:16): - Attachment: #2915 BiocHubsShiny > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Bioconductor/BiocHubsShiny > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-02-06

Unknown User (07:54:34): Unknown User (08:58:52): - Attachment: #2916 DELocal > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/dasroy/DELocal > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:57:57): Unknown User (20:45:06): - Attachment: #2917 New package submission: SVseek > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ldg21/SVseek > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:45:08): Unknown User (20:58:56): - Attachment: #2918 SVseek > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ldg21/SVseek > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:58:59): Unknown User (21:08:09): - Attachment: #2919 SVseek > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ldg21/SVseek > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-02-07

Unknown User (07:34:07): Unknown User (11:23:06): - Attachment: #2920 flowGate > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/NKInstinct/flowGate > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-02-08

Unknown User (13:43:42): - Attachment: #2921 seq.hotSPOT Bioconductor Package Submission (Sydney Grant) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/sydney-grant/seq.hotSPOT > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:43:44): Unknown User (13:58:51): - Attachment: #2922 seq.hotSPOT Bioconductor Submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/sydney-grant/seq.hotSPOT > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-02-09

Unknown User (10:19:37): - Attachment: #2923 Rarr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/grimbough/Rarr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:19:40): Unknown User (10:23:09): - Attachment: #2924 Rarr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/grimbough/Rarr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:23:12): Unknown User (10:30:33): - Attachment: #2925 Rarr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/grimbough/Rarr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:02:18): Unknown User (16:03:24):

2023-02-10

Unknown User (10:57:28): - Attachment: #2926 LoriPkgTest1 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lshep/LoriPkgTest1 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:57:31): Unknown User (11:01:44): - Attachment: #2927 Testing Package 1 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lshep/LoriPkgTest1 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:01:47): Unknown User (11:10:24): - Attachment: #2928 LoriTestPkg1 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lshep/LoriPkgTest1 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:10:26): Unknown User (11:41:53): - Attachment: #2929 LoriTestPkg1 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lshep/LoriPkgTest1 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:41:56): Unknown User (12:29:37): - Attachment: #2930 LoriPkgTest2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lshep/LoriPkgTest2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:30:40): - Attachment: #2931 LoriPkgTest1 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lshep/LoriPkgTest1 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:30:43): Unknown User (12:37:34): - Attachment: #2932 LoriTestPkg3 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lshep/LoriTestPkg3 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-02-11

Unknown User (16:30:13): - Attachment: #2933 SCArray.sat > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/zhengxwen/SCArray.sat > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:54:11):

2023-02-13

Unknown User (07:33:24):

2023-02-15

Unknown User (05:09:12): - Attachment: #2934 MultiRNAflow > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/loubator/MultiRNAflow > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:32:52): - Attachment: #2935 pfamAnalyzeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/kvittingseerup/pfamAnalyzeR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:32:55): Unknown User (10:37:22): - Attachment: #2936 pfamAnalyzeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/kvittingseerup/pfamAnalyzeR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:37:27): Unknown User (10:43:57): - Attachment: #2937 pfamAnalyzeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/kvittingseerup/pfamAnalyzeR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-02-17

Unknown User (09:06:11): Unknown User (16:50:44): - Attachment: #2938 ZygosityPredictor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CO-DKFZ/ZygosityPredictor > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:50:47):

2023-02-19

Unknown User (15:18:32): - Attachment: #2939 scviR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com:vjcitn/scviR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:18:35): Unknown User (15:18:59):

2023-02-21

Unknown User (09:24:05): Unknown User (09:24:14): Unknown User (16:33:19): - Attachment: #2940 screenCounter > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/crisprVerse/screenCounter > • > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-02-22

Unknown User (06:24:28): - Attachment: #2941 ZygosityPredictor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CO-DKFZ/ZygosityPredictor > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:51:09): Unknown User (11:51:10): Unknown User (11:51:12): Unknown User (11:51:14): Unknown User (11:51:16): Unknown User (13:09:04): Unknown User (20:15:21): - Attachment: #2942 scviR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/vjcitn/scviR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-02-24

Unknown User (08:08:39): Unknown User (08:08:41): Unknown User (11:29:59): Unknown User (20:14:11): - Attachment: #2943 BSgenomeForge > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Bioconductor/BSgenomeForge > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-02-25

Unknown User (22:02:28): - Attachment: #2944 TDbasedUFEadv > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tagtag/TDbasedUFEadv > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-02-27

Unknown User (05:54:55): - Attachment: #2945 FeatSeekR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tcapraz/FeatSeekR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-02-28

Unknown User (08:43:52): - Attachment: #2946 DESpace > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/peicai/DESpace > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-03-02

Unknown User (02:10:43): - Attachment: #2947 BiocHail > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/vjcitn/BiocHail > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-03-03

Unknown User (00:24:58): - Attachment: #2948 Rcollectl > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/vjcitn/Rcollectl > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:25:50): Unknown User (09:25:52): Unknown User (09:25:54): Unknown User (09:25:56): Unknown User (09:25:58):

2023-03-08

Unknown User (11:24:22):

2023-03-10

Unknown User (09:31:36): Unknown User (19:46:38): - Attachment: #2949 CoSIAdata > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lasseignelab/CoSIAdata > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (19:46:41):

2023-03-13

Unknown User (11:55:25): - Attachment: #2950 gsdensity > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/qingnanl/gsdensity > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:55:28): Unknown User (16:00:33): - Attachment: #2951 CoSIAdata > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lasseignelab/CoSIAdata > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-03-15

Unknown User (07:56:06): - Attachment: #2952 demuxSNP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/michaelplynch/demuxSNP > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:27:47): Unknown User (16:27:47): Unknown User (20:47:14): - Attachment: #2953 dreamlet submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/GabrielHoffman/dreamlet > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:47:17): Unknown User (20:51:52): - Attachment: #2954 dreamlet submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/GabrielHoffman/dreamlet > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:51:54): Unknown User (20:54:28): - Attachment: #2955 dreamlet submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/GabrielHoffman/dreamlet > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-03-17

Unknown User (08:40:52): - Attachment: #2956 AHMassBank package with metadata for MassBank AnnotationHub resources > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jorainer/AHMassBank > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-03-18

Unknown User (21:01:09): - Attachment: #2957 retrofit submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/qunhualilab/retrofit > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-03-20

Unknown User (04:33:57): - Attachment: #2958 pairedGSEA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/shdam/pairedGSEA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:41:31): - Attachment: #2959 Boosting Robust edgeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BandhanSarker/bRobustEdgeR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:41:34): Unknown User (07:59:00): Unknown User (07:59:07): - Attachment: #2960 Dear @BandhanSarker, > > Dear @BandhanSarker, > > > > > > The package version number, ‘0.1.0’, is not formatted > correctly. Expecting format: ‘x.99.z’. > > > > > Please fix your version number. See <http://contributions.bioconductor.org/description.html#description-ver|Bioconductor version numbers> > Please also remember to run BiocCheck::BiocCheck(‘new-package’=TRUE) on your package > before submitting a new issue. BiocCheck will look for other > Bioconductor package requirements. > > > > > [1]: http://contributions.bioconductor.org/description.html#description-ver > > [2]: https://bioconductor.org/packages/BiocCheck/ > > > > > Originally posted by @bioc-issue-bot in https://github.com/Bioconductor/Contributions/issues/2959#issuecomment-1476073918

Unknown User (08:02:18): - Attachment: #2961 Boosting robust edgeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BandhanSarker/bRobustEdgeR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:02:21):

2023-03-21

Unknown User (00:38:33): - Attachment: #2962 cfTools > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jasminezhoulab/cfTools > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (00:38:36): Unknown User (12:23:03): - Attachment: #2963 cfTools > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jasminezhoulab/cfTools > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:53:57): - Attachment: #2964 MPO.db > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/YuLab-SMU/MPO.db > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:54:00): Unknown User (14:51:59): - Attachment: #2965 HiBED > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SalasLab/HiBED > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-03-22

Unknown User (14:48:40): Unknown User (14:48:42): Unknown User (14:48:44): Unknown User (14:48:46): Unknown User (14:48:47): Unknown User (14:48:49): Unknown User (20:25:24): - Attachment: #2966 spicyWorkflow > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/spicyWorkflow > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:25:28): Unknown User (20:29:21): - Attachment: #2967 spicyWorkflow > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/spicyWorkflow > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-03-23

Unknown User (00:35:33): - Attachment: #2968 TOP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/TOP > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (00:35:35): Unknown User (00:44:19): - Attachment: #2969 TOP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/TOP > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (00:44:21): Unknown User (00:53:06): - Attachment: #2970 TOP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/TOP > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (00:53:10): Unknown User (01:03:42): - Attachment: #2971 TOP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/TOP > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:31:36): - Attachment: #2972 gdrplatfrom release [first package: gDRstyle] > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/gdrplatform/gDRstyle > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:31:39): Unknown User (15:31:40): - Attachment: #2973 mariner > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/EricSDavis/mariner > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:31:42):

2023-03-24

Unknown User (01:05:28): - Attachment: #2974 gdrplatfrom release [first package: gDRstyle] > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/gdrplatform/gDRstyle > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of gDRstyle. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (01:05:30): Unknown User (01:46:26): - Attachment: #2975 mastR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/DavisLaboratory/mastR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (02:46:43): - Attachment: #2976 gdrplatfrom release [first package: gDRstyle] > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/gdrplatform/gDRstyle > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of gDRstyle. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:19:57): - Attachment: #2977 S4Arrays > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Bioconductor/S4Arrays > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:19:59): Unknown User (11:52:23): - Attachment: #2978 S4Arrays > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Bioconductor/S4Arrays > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:25:33): - Attachment: #2979 iNETgrate > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/habilzare/iNETgrate > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (23:03:49): - Attachment: #2980 symbol.equation.gpt > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/oobianom/symbol.equation.gpt > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor [Package Submission][2] > instructions. My package is consistent with the Bioconductor > [Package Guidelines][1]. > > • [ x] I understand Bioconductor [Package Naming Policy][9] and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the [support site][3] for issues that users may > have, subscribing to the [bioc-devel][4] mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the [Bioconductor code of conduct][7] and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using [Git][5] > (optionally [via GitHub][6]).

Unknown User (23:03:50): Unknown User (23:07:51): - Attachment: #2981 symbol.equation.gpt > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/oobianom/symbol.equation.gpt > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor [Package Submission][2] > instructions. My package is consistent with the Bioconductor > [Package Guidelines][1]. > > • [x ] I understand Bioconductor [Package Naming Policy][9] and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the [support site][3] for issues that users may > have, subscribing to the [bioc-devel][4] mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the [Bioconductor code of conduct][7] and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using [Git][5] > (optionally [via GitHub][6]).

Unknown User (23:07:53): Unknown User (23:09:53): - Attachment: #2982 symbol.equation.gpt > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/oobianom/symbol.equation.gpt > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor [Package Submission][2] > instructions. My package is consistent with the Bioconductor > [Package Guidelines][1]. > > • [x] I understand Bioconductor [Package Naming Policy][9] and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the [support site][3] for issues that users may > have, subscribing to the [bioc-devel][4] mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the [Bioconductor code of conduct][7] and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using [Git][5] > (optionally [via GitHub][6]).

Unknown User (23:09:55):

2023-03-26

Unknown User (07:32:46): - Attachment: #2983 adverSCarial > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/GhislainFievet/adverSCarial > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:04:46): - Attachment: #2984 HiTIMED > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SalasLab/HiTIMED > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:04:49): Unknown User (17:24:14): - Attachment: #2985 MPO.db > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/YuLab-SMU/MPO.db > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x]The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-03-28

Unknown User (06:12:45): - Attachment: #2986 CTdata: Data companion to CTexploreR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/UCLouvain-CBIO/CTdata/ > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:40:31): - Attachment: #2987 gdrplatfrom release [second package: gDRtestData] > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/gdrplatform/gDRtestData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of gDRtestData. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:13:48): - Attachment: #2988 escheR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/boyiguo1/escheR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:39:46): - Attachment: #2989 MultimodalExperiment > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/schifferl/MultimodalExperiment > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:59:32): - Attachment: #2990 mariner > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/EricSDavis/mariner > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:59:34): Unknown User (21:08:45): - Attachment: #2991 CuratedAtlasQueryR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/stemangiola/CuratedAtlasQueryR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-03-29

Unknown User (09:00:52): - Attachment: #2992 cytoviewer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BodenmillerGroup/cytoviewer > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:41:06): - Attachment: #2993 Moonlight2R > Hi, here’s our submission for the Moonlight2R package. Thanks for reviewing it! > > > > > • Repository: https://github.com/ELELAB/Moonlight2R > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor [Package Submission][2] > instructions. My package is consistent with the Bioconductor > [Package Guidelines][1]. > > • [x] I understand Bioconductor [Package Naming Policy][9] and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the [support site][3] for issues that users may > have, subscribing to the [bioc-devel][4] mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the [Bioconductor code of conduct][7] and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using [Git][5] > (optionally [via GitHub][6]).

Unknown User (23:46:42): - Attachment: #2994 RAIDS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/KrasnitzLab/RAIDS > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (23:46:44):

2023-03-30

Unknown User (00:11:20): - Attachment: #2995 RAIDS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/KrasnitzLab/RAIDS > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (01:35:16): - Attachment: #2996 gdrplatfrom release [third package: gDRtestData] > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/gdrplatform/gDRutils > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (01:56:09): - Attachment: #2997 gdrplatform release [fourth package: gDRimport] > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/gdrplatform/gDRimport > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain the use of gDRimport. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:22:11): - Attachment: #2998 gDNAinRNAseqData: ExperimentHub resource data support package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/functionalgenomics/gDNAinRNAseqData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ X] The ‘devel’ branch for new packages and features. > • [ X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:57:26): - Attachment: #2999 CAMPP2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ELELAB/CAMPP2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:26:01): - Attachment: #3000 marinerData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/EricSDavis/marinerData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:26:05): Unknown User (17:36:55): - Attachment: #3001 MoleculeExperiment > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/MoleculeExperiment > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:38:24): - Attachment: #3002 marinerData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/EricSDavis/marinerData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-03-31

Unknown User (04:05:44): - Attachment: #3003 gdrplatform release [fifth package: gDRcore] > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/gdrplatform/gDRcore > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of gDRcore. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:28:11): - Attachment: #3004 gdrplatform release [sixth package: gDR] > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/gdrplatform/gDR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of gDR. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:29:10): Unknown User (07:29:11): Unknown User (07:29:13): Unknown User (07:29:15): Unknown User (12:54:29): Unknown User (12:55:03): Unknown User (12:55:28): Unknown User (13:00:44): Unknown User (13:04:36): Unknown User (13:05:18): Unknown User (18:06:20): - Attachment: #3005 concordexR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://pachterlab.github.io/concordexR/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:06:23): Unknown User (18:10:42): - Attachment: #3006 concordexR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/pachterlab/concordexR/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-04-03

Unknown User (05:48:50): - Attachment: #3007 PLSDAbatch > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/EvaYiwenWang/PLSDAbatch-for-Bioconductor > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:48:52): Unknown User (07:27:29): Unknown User (08:25:37): - Attachment: #3008 PLSDAbatch > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/EvaYiwenWang/PLSDAbatch > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:25:40): Unknown User (08:28:44):

2023-04-04

Unknown User (04:33:38): - Attachment: #3009 PLSDAbatch > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/EvaYiwenWang/PLSDAbatch > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-04-05

Unknown User (07:17:09): Unknown User (07:20:50): Unknown User (16:14:37): - Attachment: #3010 GRETTA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ytakemon/GRETTA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:14:40): Unknown User (16:42:10): - Attachment: #3011 GRETTA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ytakemon/GRETTA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (23:25:59): - Attachment: #3012 DMEA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BelindaBGarana/DMEA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (23:26:01):

2023-04-10

Unknown User (10:57:46): Unknown User (10:57:48): Unknown User (10:57:51): Unknown User (10:57:53): Unknown User (10:57:55): Unknown User (10:57:57): Unknown User (10:57:58): Unknown User (16:23:06): - Attachment: #3013 decontX > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/campbio/decontX > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:23:09):

2023-04-11

Unknown User (23:54:37):

2023-04-12

Unknown User (01:29:27): - Attachment: #3014 gdrplatform release [first package: gDRstyle] > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: Repository: https://github.com/gdrplatform/gDRstyle > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of gDRstyle. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (01:29:30): Unknown User (07:47:46):

2023-04-13

Unknown User (09:23:40): Unknown User (09:23:42): Unknown User (09:23:44): Unknown User (09:23:46): Unknown User (09:23:49): Unknown User (09:23:51): Unknown User (22:35:05): - Attachment: #3015 DMEA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BelindaBGarana/DMEA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-04-14

Unknown User (11:23:24):

2023-04-17

Unknown User (08:20:18): Unknown User (08:20:21): Unknown User (08:20:23): Unknown User (08:20:25): Unknown User (08:20:27): Unknown User (08:20:29): Unknown User (08:20:31): Unknown User (08:20:33): Unknown User (08:20:34):

2023-04-18

Unknown User (07:00:03): - Attachment: #3016 Submit new package ‘fenr’ > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/bartongroup/fenr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > > > > > Note: BiocCheck generates an error “Maintainer must register at the support site”. However, I am registered, see https://support.bioconductor.org/u/7369/, and my e-mail address (M.Gierlinski@dundee.ac.uk|M.Gierlinski@dundee.ac.uk) is the same as in the DESCRIPTION file. The following query: https://support.bioconductor.org/api/email/M.Gierlinski%40dundee.ac.uk returns false, indicating a problem with the bioconductor site. I raised this issue (https://support.bioconductor.org/p/88856/#9146483), but received no help. > > > > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:00:06): Unknown User (07:26:03): - Attachment: #3017 New package fenr submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/bartongroup/fenr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > > > > > Note: BiocCheck generates an error “Maintainer must register at the support site”. However, I am registered, see https://support.bioconductor.org/u/7369/, and my e-mail address (M.Gierlinski@dundee.ac.uk|M.Gierlinski@dundee.ac.uk) is the same as in the DESCRIPTION file. The following query: https://support.bioconductor.org/api/email/M.Gierlinski%40dundee.ac.uk returns false, indicating a problem with the bioconductor site. I raised this issue (https://support.bioconductor.org/p/88856/#9146483), but received no help. > > > > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:34:00): Unknown User (07:34:02): Unknown User (07:34:04):

2023-04-20

Unknown User (09:59:08): Unknown User (09:59:10): Unknown User (09:59:12): Unknown User (09:59:14): Unknown User (09:59:17): Unknown User (14:27:26): - Attachment: #3018 KMCUT > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ibkstore/kmcut > • > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-04-21

Unknown User (09:18:14):

2023-04-22

Unknown User (10:47:31): Unknown User (10:47:33): Unknown User (13:45:35): - Attachment: #3019 decontX > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/campbio/decontX > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:45:38): Unknown User (14:07:10): - Attachment: #3020 decontX > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/campbio/decontX > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-04-23

Unknown User (17:28:46):

2023-04-24

Unknown User (18:09:52): - Attachment: #3021 RNAseqCovarImpute > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/brennanhilton/RNAseqCovarImpute > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-04-26

Unknown User (07:38:20): - Attachment: #3022 GFPredict > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/reggenlab/GFPredict > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:38:22): Unknown User (13:04:06): - Attachment: #3023 MICSQTL > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/YuePan027/MICSQTL > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-04-29

Unknown User (20:37:31): - Attachment: #3024 smokingMouse > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/LieberInstitute/smokingMouse > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-05-02

Unknown User (16:09:16): - Attachment: #3025 update the EBSeq package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/wiscstatman/EBSeq > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:09:18): Unknown User (16:11:23): - Attachment: #3026 update for package EBSeq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/wiscstatman/EBSeq > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:11:26): Unknown User (17:15:06): - Attachment: #3027 RegionalST > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ziyili20/RegionalST > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-05-03

Unknown User (12:27:31): - Attachment: #3028 alabaster.files > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ArtifactDB/alabaster.files > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-05-05

Unknown User (07:27:09): - Attachment: #3029 Lheuristic > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ASPresearch/Lheuristic > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:27:12): Unknown User (10:14:27): - Attachment: #3030 HiTIMED > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SalasLab/HiTIMED > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-05-07

Unknown User (03:46:03): - Attachment: #3031 HPO.db > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/YuLab-SMU/HPO.db > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (03:47:45): Unknown User (04:11:19): - Attachment: #3032 HPO.db > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/YuLab-SMU/HPO.db > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:11:21): Unknown User (04:12:47):

2023-05-08

Unknown User (09:41:23): - Attachment: #3033 methyLImp2 submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/annaplaksienko/methyLImp2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:41:25): Unknown User (09:44:38): - Attachment: #3034 methyLImp2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/annaplaksienko/methyLImp2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:44:40): Unknown User (09:51:23): - Attachment: #3035 methyLImp2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/annaplaksienko/methyLImp2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-05-11

Unknown User (07:36:54): - Attachment: #3036 HarmonizR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/HSU-HPC/HarmonizR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:36:56): Unknown User (08:23:49): - Attachment: #3037 HarmonizR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/HSU-HPC/HarmonizR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-05-12

Unknown User (06:19:06): - Attachment: #3038 Lheuristic package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ASPresearch/Lheuristic.git > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (06:19:08): Unknown User (06:24:22): - Attachment: #3039 Lheuistic package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ASPresearch/Lheuristic > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:16:51): Unknown User (10:16:53): Unknown User (10:16:54):

2023-05-16

Unknown User (20:11:20): - Attachment: #3040 GenomicPlot > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository:https://github.com/shuye2009/GenomicPlot > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:11:22):

2023-05-17

Unknown User (10:57:09): - Attachment: #3041 orthosData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/fmicompbio/orthosData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:57:12): Unknown User (11:16:11): - Attachment: #3042 orthosData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/fmicompbio/orthosData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-05-18

Unknown User (11:15:17): - Attachment: #3043 submitting cfdnakit > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Pitithat-pu/cfdnakit > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:15:19): Unknown User (13:19:32): - Attachment: #3044 submitting new package : cfdnakit > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Pitithat-pu/cfdnakit/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:19:35): Unknown User (13:21:55): - Attachment: #3045 cfdnakit > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Pitithat-pu/cfdnakit/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:21:58): Unknown User (17:30:17): - Attachment: #3046 GenomicPlot > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository:https://github.com/shuye2009/GenomicPlot > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:32:10): - Attachment: #3047 curatedPCaData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Syksy/curatedPCaData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-05-19

Unknown User (07:20:22): Unknown User (17:07:36): - Attachment: #3048 Deep characterization of cancer drugs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CBIIT-CGBB/DeepTarget > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:07:38): Unknown User (17:15:35): - Attachment: #3049 Deep characterization of cancer drugs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yhu@mail.nih.gov/DeepTarget|//github.com/yhu@mail.nih.gov > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:15:37): Unknown User (17:19:13): - Attachment: #3050 Deep characterization of cancer drugs mechanism of action by integrating large-scale genetic and drug screens > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CBIIT-CGBB/DeepTarget > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:19:15): Unknown User (17:48:04): - Attachment: #3051 Deep characterization of cancer drugs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CBIIT-CGBB/DeepTarget > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:48:07): Unknown User (17:51:54): - Attachment: #3052 Deep characterization of cancer drugs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CBIIT-CGBB/DeepTarget > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:51:56): Unknown User (17:54:57): - Attachment: #3053 Deep characterization of cancer drugs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CBIIT-CGBB/DeepTarget > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:54:59): Unknown User (18:13:55): - Attachment: #3054 Deep characterization of cancer drugs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CBIIT-CGBB/DeepTarget > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:13:57): Unknown User (18:17:21): - Attachment: #3055 Deep characterization of cancer drugs mechanism of action by integrating large-scale genetic and drug screens. > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CBIIT-CGBB/DeepTarget > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:17:23): Unknown User (18:32:08): - Attachment: #3056 Deep characterization of cancer drugs mechanism of action by integrating large-scale genetic and drug screens > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CBIIT-CGBB/DeepTarget > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:32:11): Unknown User (18:40:13): - Attachment: #3057 Deep characterization of cancer drugs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CBIIT-CGBB/DeepTarget > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:40:15): Unknown User (18:42:44): - Attachment: #3058 Deep characterization of cancer drugs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CBIIT-CGBB/DeepTarget/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:42:47):

2023-05-20

Unknown User (14:31:19): - Attachment: #3059 multiWGCNA package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/dariotommasini/multiWGCNAdata > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:31:21): Unknown User (15:19:40): - Attachment: #3060 Deep characterization of cancer drugs mechanism of action by integrating large-scale genetic and drug screens. > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CBIIT-CGBB/DeepTarget > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:19:42): Unknown User (15:35:14): - Attachment: #3061 Deep characterization of cancer drugs mechanism of action > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CBIIT-CGBB/DeepTarget > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:35:17): Unknown User (18:05:08): - Attachment: #3062 multiWGCNAdata > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/dariotommasini/multiWGCNAdata > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:05:10): Unknown User (18:22:46): - Attachment: #3063 multiWGCNAdata > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/dariotommasini/multiWGCNAdata > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-05-22

Unknown User (10:29:00):

2023-05-23

Unknown User (08:41:58): - Attachment: #3064 iSEEindex > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/iSEE/iSEEindex > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:42:43): - Attachment: #3065 iSEEde > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/iSEE/iSEEde > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:37:18): - Attachment: #3066 Deep characterization of cancer drugs mechanism of action > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CBIIT-CGBB/DeepTarget > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-05-25

Unknown User (10:38:40): - Attachment: #3067 scMultiSim > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ZhangLabGT/scMultiSim > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:38:42): Unknown User (11:40:54): - Attachment: #3068 scMultiSim > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ZhangLabGT/scMultiSim > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-05-30

Unknown User (07:40:36): - Attachment: #3069 SARC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > https://github.com/Krutik6/SARC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:40:38):

2023-06-01

Unknown User (10:15:03): - Attachment: #3070 Request to add BERT to Bioconductor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/HSU-HPC/BERT > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:04:26): - Attachment: #3071 SARC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Krutik6/SARC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-06-02

Unknown User (09:44:48): Unknown User (11:11:05): - Attachment: #3072 beachmat.hdf5 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tatami-inc/beachmat.hdf5 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-06-09

Unknown User (14:55:47): - Attachment: #3073 GloScope > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/epurdom/GloScope > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-06-16

Unknown User (16:28:18): - Attachment: #3074 Deep characterization of cancer drugs mechanism of action by integrating large-scale genetic and drug screens > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CBIIT-CGBB/DeepTarget > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:28:21):

2023-06-20

Unknown User (10:39:33): Unknown User (10:39:35): Unknown User (10:39:37): Unknown User (10:39:39): Unknown User (10:39:41): Unknown User (10:39:42): Unknown User (10:39:44): Unknown User (10:39:46): Unknown User (12:49:04): - Attachment: #3075 mobileRNA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/KJeynesCupper/mobileRNA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:49:07): Unknown User (13:21:36): - Attachment: #3076 mobileRNA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > Repository: https://github.com/KJeynesCupper/mobileRNA > Confirm the following by editing each check box to ‘[x]’ > > > > > [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > > > > [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > > > > [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > > > > [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > > > > [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > > > > [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > [ x] The ‘devel’ branch for new packages and features. > [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > [x ] Bioconductor version control using Git > (optionally via GitHub). > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up.

2023-06-22

Unknown User (06:57:59): Unknown User (22:17:34): - Attachment: #3077 Cara1.0 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/pipaber/Cara1.0 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-06-23

Unknown User (11:30:47): Unknown User (11:30:48):

2023-06-26

Unknown User (08:53:13): Unknown User (12:10:30): - Attachment: #3078 ggkegg > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/noriakis/ggkegg > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > > > > > Some functions use snake case names instead of the camel case names specified in the guidelines. This is because the package has some functions that are intended to be used with functions in dplyr, such as mutate. If necessary, I will make the changes. Also, some functions download files from the web server and have \dontrun{} in their examples. > > > > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-06-28

Unknown User (11:11:29): - Attachment: #3079 compSPOT > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/sydney-grant/compSPOT > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-07-03

Unknown User (09:50:43): Unknown User (09:50:45): Unknown User (09:50:46): Unknown User (09:50:48): Unknown User (09:50:50):

2023-07-05

Unknown User (12:37:35): - Attachment: #3080 hicVennDiagram > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jianhong/hicVennDiagram > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-07-11

Unknown User (08:33:23): - Attachment: #3081 Submit CytoPipelineGUI package > Preliminary NOTE: this new candidate package is a ‘companion’ package of CytoPipeline (already on Bioconductor). > It implements two shiny applications that : > > • read data stored on a disk cache that was created by a preliminary pipeline run with CytoPipeline > > • make use of plotting functionalities implemented in CytoPipeline and expose them in a user interactive fashion > > • Repository: https://github.com/UCLouvain-CBIO/CytoPipelineGUI > > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-07-12

Unknown User (16:01:35): Unknown User (16:01:37):

2023-07-18

Unknown User (13:49:53): - Attachment: #3082 gDNAx > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/functionalgenomics/gDNAx > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-07-19

Unknown User (05:12:23): - Attachment: #3083 IsoBayes > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SimoneTiberi/IsoBayes > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:12:25): Unknown User (05:21:20): - Attachment: #3084 IsoBayes > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SimoneTiberi/IsoBayes > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:29:18): - Attachment: #3085 roastgsa > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BBIRBCF/roastgsa > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:29:21): Unknown User (05:34:00): - Attachment: #3086 roastgsa > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BBIRBCF/roastgsa > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-07-25

Unknown User (04:38:31): - Attachment: #3087 ClustIRR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/snaketron/ClustIRR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-07-26

Unknown User (18:49:19): - Attachment: #3088 crisprShiny > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/crisprVerse/crisprShiny > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > axgree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:49:22): Unknown User (18:50:45): - Attachment: #3089 crisprShiny > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/crisprVerse/crisprShiny > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:50:47): Unknown User (18:52:10): - Attachment: #3090 crisprShiny > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/crisprVerse/crisprShiny > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:52:12): Unknown User (19:06:19): - Attachment: #3091 crisprShiny > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/crisprVerse/crisprShiny > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-07-28

Unknown User (05:59:24): - Attachment: #3092 zitools package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/kreutz-lab/zitools > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > > > > > Justification for warnings: > The set.seed() function is used in one function (…) to ensure a random subsetting process, however make it reproducible when using the functions > > > > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:59:27): Unknown User (06:11:09): - Attachment: #3093 zitools Submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/kreutz-lab/zitools > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > > > > > Justification for one warning: set.seed is used when randomly dividing a matrix into smaller blocks to ensure a reproducible process. > > > > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (06:11:12): Unknown User (07:09:03): - Attachment: #3094 zitools submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/kreutz-lab/zitools > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > > > > > Justification for one warning: set.seed is used when randomly dividing a matrix into smaller blocks to ensure a reproducible process. > > > > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:58:21): Unknown User (10:09:43):

2023-07-29

Unknown User (09:42:58): - Attachment: #3095 scMitoMut: single cell mitochondrial mutation calling tool > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/wenjie1991/scMitoMut > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:51:55): Unknown User (22:53:54):

2023-07-31

Unknown User (07:05:40): Unknown User (12:25:15): - Attachment: #3096 Zhou Lab CytoMethIC Package Submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/zhou-lab/CytoMethIC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:25:18): Unknown User (15:28:30): - Attachment: #3097 Zhou Lab CytoMethIC Package Submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/zhou-lab/CytoMethIC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-08-01

Unknown User (16:10:16): - Attachment: #3098 Contribute MicroBioMap package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:10:18): Unknown User (16:12:07): - Attachment: #3099 Contribute MicroBioMap package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/seandavi/MicroBioMap > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:12:10): Unknown User (16:17:04): - Attachment: #3100 MicroBioMap > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/seandavi/MicroBioMap > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-08-03

Unknown User (09:23:15): - Attachment: #3101 homosapienDEE2CellScore data package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/flaviusb/homosapienDEE2CellScore > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-08-04

Unknown User (09:23:31): Unknown User (09:31:58): Unknown User (11:12:26): - Attachment: #3102 Rvisdiff > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BioinfoUSAL/Rvisdiff > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-08-07

Unknown User (09:23:39): Unknown User (09:59:10): Jiaji George Chen (11:22:05): > @Jiaji George Chen has joined the channel

2023-08-08

Unknown User (15:01:57):

2023-08-09

Unknown User (09:02:53): - Attachment: #3103 SurfR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/auroramaurizio/SurfR.git > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:02:55): Unknown User (09:05:04): - Attachment: #3104 SurfR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/auroramaurizio/SurfR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:05:07): Unknown User (13:28:39): - Attachment: #3105 SurfR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/auroramaurizio/SurfR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-08-10

Unknown User (12:39:22): - Attachment: #3106 geyser > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/davemcg/geyser > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:39:25): Unknown User (12:54:17): - Attachment: #3107 geyser > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/davemcg/geyser > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-08-11

Unknown User (01:02:41):

2023-08-13

Unknown User (16:06:34): - Attachment: #3108 simona > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jokergoo/simona > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-08-14

Unknown User (05:38:30): - Attachment: #3109 DisVar > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Khunanon-Chanasongkhram/DisVar > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:38:32): Unknown User (12:13:09): - Attachment: #3110 CardinalIO > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/kuwisdelu/CardinalIO > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-08-15

Unknown User (15:53:09): - Attachment: #3111 TSAR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CGAO123/TSAR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:56:38): - Attachment: #3112 TSAR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CGAO123/TSAR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:02:26): Unknown User (17:11:00): Unknown User (17:18:47): - Attachment: #3113 TSAR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CGAO123/TSAR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-08-16

Unknown User (04:15:42): - Attachment: #3114 Submission of package cleanse > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/martijnvanattekum/cleanse > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-08-18

Unknown User (05:12:10): - Attachment: #3115 CCPlotR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Sarah145/CCPlotR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:12:13): Unknown User (05:22:09): - Attachment: #3116 CCPlotR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Sarah145/CCPlotR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-08-21

Unknown User (21:50:21): - Attachment: #3117 hoodscanR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/DavisLaboratory/hoodscanR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-08-22

Jacques SERIZAY (17:58:47): > @Jacques SERIZAY has joined the channel

Unknown User (19:12:55): - Attachment: #3118 BiocBook > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/js2264/BiocBook > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-08-25

Unknown User (06:15:40): - Attachment: #3119 pgxRpi > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/progenetix/pgxRpi > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (06:15:43): Unknown User (06:35:21): - Attachment: #3120 pgxRpi > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/progenetix/pgxRpi > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:07:20): Unknown User (11:07:21): Unknown User (11:07:22): Unknown User (11:07:24): Unknown User (11:07:25): Unknown User (11:07:27):

2023-08-26

Unknown User (15:06:33): - Attachment: #3121 easylift > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/nahid18/easylift > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:06:35): Unknown User (15:13:50): - Attachment: #3122 easylift > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/nahid18/easylift > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-08-28

Unknown User (07:31:11): - Attachment: #3123 ginmappeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/DEAL-US/ginmappeR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:31:13): Unknown User (09:31:12): - Attachment: #3124 ginmappeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/DEAL-US/ginmappeR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:38:47): - Attachment: #3125 plasmut bioconductor submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/cancer-genomics/plasmut > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:38:49): Unknown User (13:41:33): - Attachment: #3126 plasmut bioconductor submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/cancer-genomics/plasmut > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:41:36): Unknown User (13:45:56): - Attachment: #3127 plasmut package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/cancer-genomics/plasmut > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (21:30:58): - Attachment: #3128 drugfindR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CogDisResLab/drugfindR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (21:31:00):

2023-08-30

Unknown User (16:14:59): - Attachment: #3129 gg4way > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ben-laufer/gg4way > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-08-31

Unknown User (21:51:59): - Attachment: #3130 tidySpatialExperiment > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/william-hutchison/tidySpatialExperiment > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-09-01

Unknown User (20:40:25): - Attachment: #3131 regionalpcs > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tyeulalio/regionalpcs > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-09-04

Unknown User (07:49:34): - Attachment: #3132 GNOSIS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Lydia-King/GNOSIS > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:39:08): - Attachment: #3133 iSEEpathways > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/iSEE/iSEEpathways > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-09-06

Unknown User (13:09:57): Unknown User (13:09:59): Unknown User (13:10:00): Unknown User (13:10:02): Unknown User (16:48:19): - Attachment: #3134 cfToolsData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jasminezhoulab/cfToolsData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:48:22):

2023-09-07

Unknown User (08:08:43): Unknown User (13:55:03):

2023-09-08

Unknown User (03:34:12): - Attachment: #3135 ggsc > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/YuLab-SMU/ggsc > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (03:34:14): Unknown User (03:39:58): - Attachment: #3136 ggsc > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/YuLab-SMU/ggsc > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (06:41:06): - Attachment: #3137 CTexploreR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/UCLouvain-CBIO/CTexploreR.git > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (06:41:08): Unknown User (06:53:31): - Attachment: #3138 CTexploreR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/UCLouvain-CBIO/CTexploreR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:59:59): - Attachment: #3139 spbtest5 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lshep/spbtest5.git > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:00:01): Unknown User (08:03:12): - Attachment: #3140 spbtest5 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lshep/spbtest5 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:03:15): Unknown User (08:06:35): - Attachment: #3141 spbtest5 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lshep/spbtest5 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:06:37): Unknown User (08:12:30):

2023-09-12

Unknown User (03:59:43): - Attachment: #3142 limpca > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ManonMartin/limpca > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:24:05): Unknown User (10:25:06): - Attachment: #3143 spbtest5 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lshep/spbtest5 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:33:54): Unknown User (10:49:22): - Attachment: #3144 spbtest5 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lshep/spbtest5 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:49:25): Unknown User (12:12:05): - Attachment: #3145 spbtest5 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lshep/spbtest5 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:13:57): Unknown User (13:31:12): Unknown User (13:31:13): Unknown User (13:31:15): Unknown User (13:31:16): Unknown User (14:02:41): Unknown User (14:32:11): Unknown User (14:40:01): - Attachment: #3146 DeProViR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mrbakhsh/DeProViR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:40:04): Unknown User (14:42:18): - Attachment: #3147 DeProViR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mrbakhsh/DeProViR > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:42:20): Unknown User (14:51:34): - Attachment: #3148 DeProViR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mrbakhsh/DeProViR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-09-13

Unknown User (05:09:49): - Attachment: #3149 limpca > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ManonMartin/limpca > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:06:49): - Attachment: #3150 lemur > • Repository: https://github.com/const-ae/lemur > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:06:52): Unknown User (09:20:28): - Attachment: #3151 drugfindR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CogDisResLab/drugfindR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:30:20): - Attachment: #3152 lemur > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/const-ae/lemur > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:17:38): - Attachment: #3153 betaHMM > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/koyelucd/betaHMM > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:17:41): Unknown User (11:28:42): - Attachment: #3154 betaHMM submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/koyelucd/betaHMM > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-09-14

Unknown User (10:04:40):

2023-09-18

Unknown User (06:30:59): - Attachment: #3155 igvShiny submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/gladkia/igvShiny > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (06:46:38): - Attachment: #3156 saseR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/statOmics/saseR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-09-19

Unknown User (06:12:22): - Attachment: #3157 New Kinship2 package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/LouisLeNezet/kinship2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (06:12:25): Unknown User (08:45:28): - Attachment: #3158 dar > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/MicrobialGenomics-IrsicaixaOrg/dar > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:43:58): - Attachment: #3159 Kinship2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/LouisLeNezet/kinship2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:15:44): - Attachment: #3160 raerdata > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rnabioco/raerdata > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-09-20

Jaykishan (05:05:03): > @Jaykishan has joined the channel

2023-09-21

Unknown User (09:15:21): Unknown User (09:15:23): Unknown User (09:15:25): Unknown User (10:23:23): Unknown User (20:45:34): - Attachment: #3161 scider > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ChenLaboratory/scider > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-09-23

Unknown User (08:39:55): - Attachment: #3162 BioCartaImage > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jokergoo/BioCartaImage/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-09-24

Unknown User (18:25:53): - Attachment: #3163 CRISPRball > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/j-andrews7/CRISPRball > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-09-26

Unknown User (07:00:14): Unknown User (12:35:55): - Attachment: #3164 cfToolsData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jasminezhoulab/cfToolsData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:06:01): - Attachment: #3165 SomaScan.db > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SomaLogic/SomaScan.db > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:40:09): - Attachment: #3166 PIPETS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/qfurumo/PIPETS > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:21:51): - Attachment: #3167 lute > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/metamaden/lute > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-09-27

Unknown User (08:57:14): - Attachment: #3168 JASPAR2024 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/da-bar/JASPAR2024 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:31:46): - Attachment: #3169 methodical > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/richardheery/methodical > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:56:51): - Attachment: #3170 gatom > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ctlab/gatom > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:18:34): - Attachment: #3171 enrichViewNet > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/adeschen/enrichViewNet > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:18:36): Unknown User (21:55:33): - Attachment: #3172 enrichViewNet > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/adeschen/enrichViewNet > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (21:55:35): Unknown User (22:07:48): - Attachment: #3173 enrichViewNet > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/adeschen/enrichViewNet > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (23:03:05): - Attachment: #3174 phantasusLite > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ctlab/phantasusLite > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-09-28

Unknown User (00:27:46): - Attachment: #3175 darr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/baerlachlan/darr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (01:21:39): - Attachment: #3176 QTLExperiment > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/dunstone-a/QTLExperiment > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (01:21:41): Unknown User (03:01:50): - Attachment: #3177 QTLExperiment > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/dunstone-a/QTLExperiment > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:26:43): - Attachment: #3178 pathlinkR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/hancockinformatics/pathlinkR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:26:46): Unknown User (16:38:30): - Attachment: #3179 pathlinkR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/hancockinformatics/pathlinkR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-09-29

Unknown User (04:26:54): - Attachment: #3180 peakCombiner > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Novartis/peakCombiner > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:26:55): Unknown User (04:32:18): - Attachment: #3181 peakCombiner > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Novartis/peakCombiner > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:32:20): Unknown User (06:53:36): Unknown User (07:04:53): - Attachment: #3182 SpatialDatasets > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/SpatialDatasets > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:04:55): Unknown User (07:08:13): - Attachment: #3183 SpatialDatasets > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/SpatialDatasets > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:08:15): Unknown User (07:09:48): - Attachment: #3184 SpatialDatasets > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/SpatialDatasets > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:09:50): Unknown User (07:12:55): - Attachment: #3185 SpatialDatasets > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/SpatialDatasets > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:31:14): - Attachment: #3186 tadar > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/baerlachlan/tadar > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:16:42): - Attachment: #3187 MGnifyR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/EBI-Metagenomics/MGnifyR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:16:45): Unknown User (10:05:33): - Attachment: #3188 peakCombiner > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Novartis/peakCombiner > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:35:16): - Attachment: #3189 TumourMethData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/richardheery/TumourMethData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:38:08): - Attachment: #3190 HCATonsilData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/massonix/HCATonsilData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:00:29): - Attachment: #3191 MGnifyR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/EBI-Metagenomics/MGnifyR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:26:46): Unknown User (16:27:39): - Attachment: #3192 Pedigree > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/LouisLeNezet/Pedigree > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:17:07): - Attachment: #3193 MSstatsBig > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Vitek-Lab/MSstatsBig > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ ]x The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:25:49): - Attachment: #3194 plyinteractions > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tidyomics/plyinteractions > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:22:21): - Attachment: #3195 SpaceMarkers > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/atuldeshpande/SpaceMarkers > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:22:24): Unknown User (20:48:22): - Attachment: #3196 SpaceMarkers > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/atuldeshpande/SpaceMarkers > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:54:57): - Attachment: #3197 knowYourCG > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/zhou-lab/knowYourCG > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-10-02

Unknown User (07:44:06): Unknown User (07:44:07): Unknown User (07:44:09): Unknown User (07:44:10): Unknown User (07:44:12): Unknown User (07:44:14):

2023-10-03

Unknown User (16:43:06): - Attachment: #3198 Banksy > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/prabhakarlab/Banksy > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:43:08): Unknown User (16:47:36): - Attachment: #3199 Banksy > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/prabhakarlab/Banksy > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:47:38): Unknown User (16:51:53): - Attachment: #3200 Banksy > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/prabhakarlab/Banksy > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:51:56): Unknown User (17:08:31): - Attachment: #3201 Banksy > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/prabhakarlab/Banksy > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:58:01): - Attachment: #3202 CAM3 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ChiungTingWu/CAM3 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:58:04):

2023-10-04

Unknown User (10:45:25): Unknown User (10:47:20): - Attachment: #3203 Pedixplorer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/LouisLeNezet/Pedixplorer > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:01:16): - Attachment: #3204 CAM3 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ChiungTingWu/CAM3 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:01:20): Unknown User (18:57:00): - Attachment: #3205 CAM3 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ChiungTingWu/CAM3 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-10-05

Unknown User (07:03:12): - Attachment: #3206 inferCSN > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mengxu98/inferCSN > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:03:15): Unknown User (07:16:03): - Attachment: #3207 inferCSN > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mengxu98/inferCSN > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:16:07): Unknown User (07:24:03): - Attachment: #3208 inferCSN > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mengxu98/inferCSN > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:24:06): Unknown User (07:32:49): - Attachment: #3209 inferCSN > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mengxu98/inferCSN > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:32:52): Unknown User (07:44:11): - Attachment: #3210 inferCSN > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mengxu98/inferCSN > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-10-06

Unknown User (09:02:04): - Attachment: #3211 Submission package spillR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/marcoguazzini/spillR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:02:06): Unknown User (09:08:53): - Attachment: #3212 spillR package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/marcoguazzini/spillR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:08:56): Unknown User (09:59:14): Unknown User (10:14:05): - Attachment: #3213 spillR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/marcoguazzini/spillR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:14:08): Unknown User (10:21:06): - Attachment: #3214 spillR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/marcoguazzini/spillR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:12:04): Unknown User (11:12:06): Unknown User (11:12:08): Unknown User (11:12:10): Unknown User (11:14:20): Unknown User (13:13:32):

2023-10-09

Unknown User (23:05:06): - Attachment: #3215 TCGAplot > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tjhwangxiong/TCGAplot > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (23:05:09): Unknown User (23:23:56): - Attachment: #3216 TCGAplot > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tjhwangxiong/TCGAplot > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-10-11

Unknown User (10:24:37):

2023-10-12

Unknown User (15:01:04): - Attachment: #3217 AlphaMissense > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mtmorgan/AlphaMissense > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:01:07): Unknown User (15:04:18): - Attachment: #3218 AlphaMissense > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mtmorgan/AlphaMissense > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:04:20): Unknown User (15:08:07): - Attachment: #3219 AlphaMissense > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mtmorgan/AlphaMissense > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-10-13

Unknown User (12:04:35): Unknown User (13:08:58): Unknown User (13:09:00): Unknown User (13:09:02): Unknown User (13:09:04): Unknown User (13:09:06): Unknown User (13:09:08): Unknown User (13:09:10):

2023-10-16

Unknown User (10:39:51): Unknown User (10:39:52):

2023-10-17

Unknown User (14:25:48): Unknown User (14:25:50): Unknown User (14:25:52): Unknown User (14:25:53): Unknown User (14:25:55): Unknown User (14:25:57): Unknown User (14:25:59): Unknown User (14:26:01):

2023-10-18

Unknown User (03:07:54): - Attachment: #3220 mhAnalysis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/huerqiang/mhAnalysis > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:41:32): Unknown User (14:41:33): Unknown User (15:06:20): Unknown User (15:07:53): Unknown User (15:09:14): Unknown User (15:38:06): - Attachment: #3221 AlphaMissenseR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mtmorgan/AlphaMissenseR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-10-20

Unknown User (08:02:22): Unknown User (15:47:18): - Attachment: #3222 CustomGenome > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://gitlab.com/mtekman/customgenome > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:47:20): Unknown User (15:53:03): - Attachment: #3223 CustomGenome > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mtekman/customgenome > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:53:06): Unknown User (15:54:58): - Attachment: #3224 CustomGenome > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mtekman/CustomGenome > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-10-21

Unknown User (10:25:35): Unknown User (10:25:36): Unknown User (10:25:37): Unknown User (10:25:39): Unknown User (10:25:41): Unknown User (10:25:42): Unknown User (10:25:44):

2023-10-23

Unknown User (17:27:25): Unknown User (17:27:26):

2023-10-27

Unknown User (22:14:43): Unknown User (22:16:17): - Attachment: #3225 inferCSN > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mengxu98/inferCSN > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:16:20): Unknown User (22:17:09):

2023-10-28

Unknown User (04:30:10): - Attachment: #3226 txdbmaker > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Bioconductor/txdbmaker > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-11-01

Unknown User (04:00:53): - Attachment: #3227 faers > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Yunuuuu/faers > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:56:17): Unknown User (16:56:19): Unknown User (16:56:20): Unknown User (16:56:22): Unknown User (19:53:36):

2023-11-06

Unknown User (15:17:53):

2023-11-07

Unknown User (09:40:46): Unknown User (09:43:59): - Attachment: #3228 inferCSN > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mengxu98/inferCSN > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:44:03): Unknown User (09:44:48): Unknown User (12:46:55): - Attachment: #3229 OHCA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/js2264/OHCA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:46:58): Unknown User (12:49:24): - Attachment: #3230 OHCA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/js2264/OHCA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:49:26): Unknown User (12:52:43): - Attachment: #3231 OHCA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/js2264/OHCA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:52:46):

2023-11-09

Unknown User (15:37:08): Unknown User (16:10:07): - Attachment: #3232 OHCA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/js2264/OHCA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-11-13

Unknown User (04:18:30): - Attachment: #3233 PLSDAbatch > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/EvaYiwenWang/PLSDAbatch > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:18:34): Unknown User (08:51:40): Unknown User (10:20:10):

2023-11-14

Unknown User (08:36:37): Unknown User (08:36:39): Unknown User (08:37:37):

2023-11-20

Unknown User (09:19:07): Unknown User (10:05:54): Unknown User (10:35:19): Unknown User (10:52:55):

2023-11-21

Unknown User (08:49:37):

2023-11-23

Unknown User (18:56:44): - Attachment: #3234 GraphSpace: A lightweight package for representing large igraph objects in a normalized coordinate system. > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/sysbiolab/GraphSpace > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:19:30): - Attachment: #3235 RGraphSpace: A lightweight package for representing large igraph objects in a normalized coordinate system. > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/sysbiolab/RGraphSpace > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:20:38):

2023-11-27

Unknown User (12:13:04): Unknown User (12:13:06): Unknown User (12:13:07):

2023-11-28

Unknown User (13:11:29):

2023-11-30

Unknown User (13:24:42): Unknown User (18:34:30): - Attachment: #3236 Error with sesameDataCache() > I previously ran sesame no problem with version 3.17. However, since updating to version 3.18, I am having issues with the sesameDataCache() function. > > > > > This is the code I ran: > if (!require("BiocManager", quietly = TRUE)) > install.packages("BiocManager") > BiocManager::install(version="3.18") > BiocManager::install("sesame", force=TRUE) > BiocManager::install("sesameData", force=TRUE) > > > > > BiocManager::install("ExperimentHub", force=TRUE) > BiocManager::install("BiocFileCache", force=TRUE) > getwd() > sessionInfo() > library(sesame) > sesame_checkVersion() > library(sesameData) > sesameDataCache() > packageVersion("sesameData") > > > > > > > > This is the error message: > sesame_checkVersion() > SeSAMe requires matched versions of R, sesame, sesameData and ExperimentHub. > Here is the current versions installed: > R: 4.3.1 > Bioconductor: 3.18 > sesame: 1.20.0 > sesameData: 1.20.0 > ExperimentHub: 2.10.0 > > > library(sesameData) > > sesameDataCache() > > Metadata (N=91): > > > > > ExperimentHub Caching fails: > error in evaluating the argument ‘x’ in selecting a method for function ‘query’: Failed to collect lazy table. > Caused by error in db_collect(): > ! Arguments in ... must be used. > :heavy_multiplication_x: Problematic argument: > • ..1 = Inf > :information_source: Did you misspell an argument name? > > > > > I have no idea how to fix this… as I am extremely new to R. Any help would be appreciated.

Unknown User (18:34:32): Unknown User (18:36:04): - Attachment: #3237 Error with SesameDataCache() > zwdzwd > / > sesame > > > > > I previously ran sesame no problem with version 3.17. However, since updating to version 3.18, I am having issues with the sesameDataCache() function. > > > > > This is the code I ran: > if (!require("BiocManager", quietly = TRUE)) > install.packages("BiocManager") > BiocManager::install(version="3.18") > BiocManager::install("sesame", force=TRUE) > BiocManager::install("sesameData", force=TRUE) > > > > > BiocManager::install("ExperimentHub", force=TRUE) > BiocManager::install("BiocFileCache", force=TRUE) > getwd() > sessionInfo() > library(sesame) > sesame_checkVersion() > library(sesameData) > sesameDataCache() > packageVersion("sesameData") > > > > > This is the error message: > sesame_checkVersion() > SeSAMe requires matched versions of R, sesame, sesameData and ExperimentHub. > Here is the current versions installed: > R: 4.3.1 > Bioconductor: 3.18 > sesame: 1.20.0 > sesameData: 1.20.0 > ExperimentHub: 2.10.0 > > > > > library(sesameData) > sesameDataCache() > Metadata (N=91): > > > > > ExperimentHub Caching fails: > error in evaluating the argument ‘x’ in selecting a method for function ‘query’: Failed to collect lazy table. > Caused by error in db_collect(): > ! Arguments in … must be used. > :heavy_multiplication_x: Problematic argument: > • ..1 = Inf > :information_source: Did you misspell an argument name? > > > > > I have no idea how to fix this… as I am extremely new to R. Any help would be appreciated.

Unknown User (18:36:04):

2023-12-02

Unknown User (14:43:17): - Attachment: #3238 GAClustR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/frankcsquared/GAClustR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:43:19): Unknown User (14:51:02): - Attachment: #3239 GAClustR: Genetic Algorithms to Enhance Clustering of Differential Gene Expression Data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/frankcsquared/GAClustR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:51:05): Unknown User (14:56:05): - Attachment: #3240 GAClustR: Genetic Algorithms to Enhance Clustering of Differential Gene Expression Data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/frankcsquared/GAClustR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:56:08): Unknown User (15:01:15): - Attachment: #3241 GAClustR: Genetic Algorithms to Enhance Clustering of Differential Gene Expression Data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/frankcsquared/GAClustR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:01:17): Unknown User (15:09:27): - Attachment: #3242 GAClustR: Genetic Algorithms for Enhancing Clustering of Gene Expression Data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/frankcsquared/GAClustR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:09:30): Unknown User (15:15:21): - Attachment: #3243 GAClustR: Genetic Algorithms for Enhancing Clustering of Gene Expression Data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/frankcsquared/GAClustR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:15:23): Unknown User (15:37:50): - Attachment: #3244 GAClustR: Genetic Algorithms to Enhance Clustering of Differential Gene Expression Data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/frankcsquared/GAClustR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-12-04

Unknown User (06:01:41): - Attachment: #3245 PIUMA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BioinfoMonzino/PIUMA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-12-05

Unknown User (13:31:58): Unknown User (13:31:59): Unknown User (13:32:01): Unknown User (15:18:53): - Attachment: #3246 tidyCoverage > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/js2264/tidyCoverage > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:18:55): Unknown User (15:21:12): - Attachment: #3247 tidyCoverage > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/js2264/tidyCoverage > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:21:14): Unknown User (15:39:08): - Attachment: #3248 tidyCoverage > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/js2264/tidyCoverage > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-12-06

Unknown User (08:41:12): - Attachment: #3249 MIRit > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jacopo-ronchi/MIRit > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:06:18): - Attachment: #3250 rawDiag > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/cpanse/rawDiag > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput omics data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:06:20): Unknown User (10:11:41): - Attachment: #3251 rawDiag > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > > Repository: https://github.com/cpanse/rawDiag > > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > > [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > [x] I have read the Bioconductor [Package Submission](https://bioconductor.org/developers/package-submission/) > instructions. My package is consistent with the Bioconductor > [Package Guidelines](https://contributions.bioconductor.org/). > > [x] I understand Bioconductor [Package Naming Policy](https://bioconductor.org/developers/package-submission/#naming) and acknowledge > Bioconductor may retain use of package name. > > [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput omics data. > > [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the [support site](https://support.bioconductor.org/) for issues that users may > have, subscribing to the [bioc-devel](https://stat.ethz.ch/mailman/listinfo/bioc-devel) mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > [x ] I am familiar with the [Bioconductor code of conduct](https://bioconductor.org/about/code-of-conduct/) and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > > [x] The 'devel' branch for new packages and features. > [x] The stable 'release' branch, made available every six > months, for bug fixes. > [x] Bioconductor version control using [Git](http://bioconductor.org/developers/how-to/git/) > (optionally [via GitHub](http://bioconductor.org/developers/how-to/git/sync-existing-repositories/)). > > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up.

2023-12-08

Unknown User (12:08:25): Unknown User (13:43:55):

2023-12-12

Unknown User (05:03:47): - Attachment: #3252 ClustAll > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/TranslationalBioinformaticsUnit/ClustAll > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:03:50): Unknown User (05:28:35): - Attachment: #3253 ClustAll > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/translationalBioinformaticsUnit/ClustAll > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-12-13

Unknown User (15:23:31): - Attachment: #3254 VisiumIO > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/waldronlab/VisiumIO > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-12-14

Unknown User (06:56:37): Unknown User (13:07:12): - Attachment: #3255 TENxXeniumData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mrbakhsh/TENxXeniumData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-12-21

Unknown User (13:26:24): Unknown User (13:27:43):

2023-12-22

Unknown User (08:36:22): - Attachment: #3256 Domino2 inference of cell-cell communication > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/FertigLab/domino2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:36:25): Unknown User (08:57:34): - Attachment: #3257 Domino2 inference of cell-cell communication > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:57:36): Unknown User (08:58:46): - Attachment: #3258 Domino2 inference of cell-cell communication > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/FertigLab/domino2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:58:50): Unknown User (09:13:32): - Attachment: #3259 domino2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/FertigLab/domino2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2023-12-24

Unknown User (06:25:08): - Attachment: #3260 RNASeqHelper > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mtekman/rnaseqhelper > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (06:25:10): Unknown User (06:27:04): - Attachment: #3261 RNASeqHelper > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mtekman/RNASeqHelper > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:34:12): - Attachment: #3262 TraRe > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ubioinformat/TraRe > > > > > This package was already a Bioconductor package, but was deprecated because one of its dependencies (vbsr) was deleted from CRAN, and we did not fix that in time. Hence, im creating a new submission process. Please let me know if this is the right way to have TraRe again as a Bioconductor package. The main branch of this package has already no error nor warnings. > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:34:14): Unknown User (18:02:10): - Attachment: #3263 TraRe > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ubioinformat/TraRe > > > > > This package was already a Bioconductor package, but was deprecated because one of its dependencies (vbsr) was deleted from CRAN, and we did not fix that in time. Hence, im creating a new submission process. Please let me know if this is the right way to have TraRe again as a Bioconductor package. The main branch of this package has already no error nor warnings. > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:02:13):

2023-12-27

Unknown User (09:27:13): Unknown User (09:27:52): Unknown User (09:28:39): Unknown User (09:29:40): Unknown User (09:47:29): Unknown User (09:49:02):

2023-12-28

Unknown User (09:30:35): - Attachment: #3264 tpSVG > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/boyiguo1/tpSVG > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-01-02

Unknown User (17:12:29): - Attachment: #3265 DegCre package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/brianSroberts/DegCre > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-01-07

Unknown User (16:20:10): - Attachment: #3266 ath1121501frmavecs: Annotation Package for frma > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/RiviereQuentin/ath1121501frmavecs > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:20:13): Unknown User (22:42:00): - Attachment: #3267 Submission of the tidyomics package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tidyomics/tidyomics > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:42:02): Unknown User (23:38:52): - Attachment: #3268 Submission of the tidyomics package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tidyomics/tidyomics > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-01-08

Unknown User (07:32:14):

2024-01-09

Unknown User (07:50:27): Unknown User (07:50:28):

2024-01-14

Unknown User (19:35:54): - Attachment: #3269 TransOmicsData data package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/PYangLab/TransOmicData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (19:35:56): Unknown User (19:40:47): - Attachment: #3270 TransOmicsData ExperimentHub package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/PYangLab/TransOmicsData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-01-15

Unknown User (03:03:55): - Attachment: #3271 epiregulon > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/xiaosaiyao/epiregulon > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (19:20:46): - Attachment: #3272 cypress > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/renlyly/cypress > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-01-16

Unknown User (07:53:59):

2024-01-17

Unknown User (07:29:27): - Attachment: #3273 dinoR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/xxxmichixxx/dinoR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:56:30): - Attachment: #3274 biocroxytest > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/xec-cm/biocroxytest > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-01-23

Unknown User (06:53:20): - Attachment: #3275 transmogR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/smped/transmogR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (06:53:22): Unknown User (06:56:59): - Attachment: #3276 transmogR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/smped/transmogR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (06:57:01): Unknown User (07:05:27): - Attachment: #3277 transmogR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/smped/transmogR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-01-24

Unknown User (10:24:22): - Attachment: #3278 spoon > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/kinnaryshah/spoon > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:27:41): Unknown User (10:36:45): Unknown User (14:33:49): Unknown User (14:39:59):

2024-01-25

Unknown User (17:25:06): - Attachment: #3279 gypsum > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/LTLA/gypsum > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:25:09): Unknown User (17:31:25): - Attachment: #3280 gypsum > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/LTLA/gypsum > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-01-26

Unknown User (07:40:37): Unknown User (07:40:38): Unknown User (07:40:39): Unknown User (07:40:40): Unknown User (07:54:49):

2024-01-30

Unknown User (10:25:48): - Attachment: #3281 Submit CytoMDS package > • Repository: https://github.com/UCLouvain-CBIO/CytoMDS > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (21:47:47): - Attachment: #3282 CaMutQC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/likelet/CaMutQC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (21:47:49): Unknown User (22:44:18): - Attachment: #3283 CaMutQC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/likelet/CaMutQC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:44:20):

2024-02-01

Unknown User (13:42:48): Unknown User (15:24:32): - Attachment: #3284 sketchR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/fmicompbio/sketchR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:32:45):

2024-02-05

Unknown User (08:13:13): Unknown User (08:49:56): Unknown User (08:49:57): Unknown User (08:49:58): Unknown User (20:19:07): - Attachment: #3285 Hub package submission: EPICv2manifest > Hi BioC, > > > > > Here is a AnnotationHub submission for the Illumina Infinium MethylationEPIC v2.0 kit probe manifest, containing the complete Illumina manifest plus extra columns describing: > > • Recommendations, based on real data, for dealing with replicated probes mapping to the same CpG locus > • Flagging of in silico-predicted cross-hybridising probes, and where there is evidence from real data, the positions of their more likely off-targets > • Degree of concordance with matched WGBS samples > • Probe histories from previous array versions > > > > > I’ve been in contact with Lori regarding the deposit of the data.frame in Data Lake; am happy to do so once I receive the token. > > > > > Best, > Tim > > > > > • Repository: https://github.com/timpeters82/EPICv2manifest > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor [Package Submission][2] > instructions. My package is consistent with the Bioconductor > [Package Guidelines][1]. > > • [x] I understand Bioconductor [Package Naming Policy][9] and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the [support site][3] for issues that users may > have, subscribing to the [bioc-devel][4] mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the [Bioconductor code of conduct][7] and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using [Git][5] > (optionally [via GitHub][6]).

2024-02-06

Unknown User (09:42:31): - Attachment: #3286 findIPs: a new R package to detect influential points for feature rankings > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ShuoStat/findIPs > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:42:33): Unknown User (10:28:16): - Attachment: #3287 findIPs: a new R package for detecting influential points of feature rankings > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ShuoStat/findIPs > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:28:19): Unknown User (10:54:32): - Attachment: #3288 findIPs: a new package to detect influential points for feature rankings > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ShuoStat/findIPs > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-02-07

Unknown User (05:17:52): - Attachment: #3289 SCIntRuler > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yuelyu21/SCIntRuler > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:17:55): Unknown User (16:48:39): - Attachment: #3290 muleaData ExperimentHubData Bioconductor package > Dear BioC Team, > > > > > Here we provide the muleaData ExperimentHubData Bioconductor package for the mulea R package. mulea is a comprehensive overrepresentation and functional enrichment analyser R package which reads ontologies (gene and protein sets) in a standardised GMT (Gene Matrix Transposed) format. We provide these GMT files for 27 different model organisms, ranging from Escherichia coli to human, all acquired from publicly available data sources. The GMT files are provided with multiple gene and protein identifiers such as UniProt protein IDs, Entrez, Gene Symbol, and Ensembl gene IDs. The GMT files and the scripts we applied to create them are available at the GMT_files_for_mulea repository. For the muleaData we read these GMT files with the mulea::read_gmt() function and saved it to .rds files with the standard R saveRDS() function. > I’ve got the SAS token from Lori Shepard and uploaded the .rds files to the Azure Data Lake. She wrote that the data is now added: > > > > query(eh, "muleaData") > ExperimentHub with 879 records > # snapshotDate(): 2024-02-07 > # $dataprovider: muleaData > # $species: Drosophila melanogaster, Homo sapiens, Mus musculus, Caenorhabdi... > # $rdataclass: data.frame > # additional mcols(): taxonomyid, genome, description, > # coordinate_1_based, maintainer, rdatadateadded, preparerclass, tags, > # rdatapath, sourceurl, sourcetype > # retrieve records with, e.g., 'object[["EH8571"]]' > > title > EH8571 | Genomic_location_Ensembl_Arabidopsis_thaliana_10genes_EnsemblID.rds > EH8572 | Genomic_location_Ensembl_Arabidopsis_thaliana_10genes_EntrezID.rds > EH8573 | Genomic_location_Ensembl_Arabidopsis_thaliana_10genes_GeneSymbol... > EH8574 | Genomic_location_Ensembl_Arabidopsis_thaliana_10genes_UniprotID.rds > EH8575 | Genomic_location_Ensembl_Arabidopsis_thaliana_20genes_EnsemblID.rds > ... ... > EH9445 | Genomic_location_Ensembl_Zea_mays_5genes_UniprotID.rds > EH9446 | Protein_domain_PFAM_Zea_mays_EnsemblID.rds > EH9447 | Protein_domain_PFAM_Zea_mays_EntrezID.rds > EH9448 | Protein_domain_PFAM_Zea_mays_GeneSymbol.rds > EH9449 | Protein_domain_PFAM_Zea_mays_UniprotID.rds > > > > > > Best wishes, > Eszter Ari > > > > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ELTEbioinformatics/muleaData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:48:41): Unknown User (16:50:48): - Attachment: #3291 muleaData ExperimentHubData Bioconductor package > Dear BioC Team, > > > > > Here we provide the muleaData ExperimentHubData Bioconductor package for the mulea (ELTEbioinformatics/mulea on github) R package. mulea is a comprehensive overrepresentation and functional enrichment analyser R package which reads ontologies (gene and protein sets) in a standardised GMT (Gene Matrix Transposed) format. We provide these GMT files for 27 different model organisms, ranging from Escherichia coli to human, all acquired from publicly available data sources. The GMT files are provided with multiple gene and protein identifiers such as UniProt protein IDs, Entrez, Gene Symbol, and Ensembl gene IDs. The GMT files and the scripts we applied to create them are available at the GMT_files_for_mulea (ELTEbioinformatics/GMT_files_for_mulea on github) repository. For the muleaData we read these GMT files with the mulea::read_gmt() function and saved it to .rds files with the standard R saveRDS() function. > I’ve got the SAS token from Lori Shepard and uploaded the .rds files to the Azure Data Lake. She wrote that the data is now added: > > > > query(eh, "muleaData") > ExperimentHub with 879 records > # snapshotDate(): 2024-02-07 > # $dataprovider: muleaData > # $species: Drosophila melanogaster, Homo sapiens, Mus musculus, Caenorhabdi... > # $rdataclass: data.frame > # additional mcols(): taxonomyid, genome, description, > # coordinate_1_based, maintainer, rdatadateadded, preparerclass, tags, > # rdatapath, sourceurl, sourcetype > # retrieve records with, e.g., 'object[["EH8571"]]' > > title > EH8571 | Genomic_location_Ensembl_Arabidopsis_thaliana_10genes_EnsemblID.rds > EH8572 | Genomic_location_Ensembl_Arabidopsis_thaliana_10genes_EntrezID.rds > EH8573 | Genomic_location_Ensembl_Arabidopsis_thaliana_10genes_GeneSymbol... > EH8574 | Genomic_location_Ensembl_Arabidopsis_thaliana_10genes_UniprotID.rds > EH8575 | Genomic_location_Ensembl_Arabidopsis_thaliana_20genes_EnsemblID.rds > ... ... > EH9445 | Genomic_location_Ensembl_Zea_mays_5genes_UniprotID.rds > EH9446 | Protein_domain_PFAM_Zea_mays_EnsemblID.rds > EH9447 | Protein_domain_PFAM_Zea_mays_EntrezID.rds > EH9448 | Protein_domain_PFAM_Zea_mays_GeneSymbol.rds > EH9449 | Protein_domain_PFAM_Zea_mays_UniprotID.rds > > > > > > Best wishes, > Eszter Ari > > > > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ELTEbioinformatics/muleaData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-02-08

Unknown User (03:25:06): - Attachment: #3292 SCIntRuler > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yuelyu21/SCIntRuler > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (03:25:08): Unknown User (09:42:22): - Attachment: #3293 MouseAgingData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ccb-hms/MouseAgingData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:21:35): - Attachment: #3294 SCIntRuler > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: There are 32738 genes and 5900 cells in this data. > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:21:37): Unknown User (15:23:46): - Attachment: #3295 SCIntRuler > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yuelyu21/SCIntRuler > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-02-09

Unknown User (07:30:31): Unknown User (11:04:40): - Attachment: #3296 New package Pirat > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/prostarproteomics/Pirat > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:04:42):

2024-02-10

Unknown User (14:47:18): - Attachment: #3297 genetic.algo.optimizeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:47:20): Unknown User (14:53:11): - Attachment: #3298 genetic.algo.optimizeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/danymukesha/genetic.algo.optimizeR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:53:13): Unknown User (14:57:23): - Attachment: #3299 genetic.algo.optimizeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/danymukesha/genetic.algo.optimizeR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:57:24): Unknown User (15:05:05): - Attachment: #3300 genetic.algo.optimizeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/danymukesha/genetic.algo.optimizeR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:05:07): Unknown User (15:08:14): - Attachment: #3301 genetic.algo.optimizeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/danymukesha/genetic.algo.optimizeR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:08:16): Unknown User (15:09:06): - Attachment: #3302 genetic.algo.optimizeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/danymukesha/genetic.algo.optimizeR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:09:08): Unknown User (15:10:01): - Attachment: #3303 genetic.algo.optimizeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/danymukesha/genetic.algo.optimizeR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:10:03): Unknown User (15:14:19): - Attachment: #3304 genetic.algo.optimizeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/danymukesha/genetic.algo.optimizeR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-02-11

Unknown User (23:44:03): - Attachment: #3305 corrmeta > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/wsjung/corrmeta > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (23:44:06):

2024-02-12

Unknown User (00:11:23): - Attachment: #3306 corrmeta > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (00:11:24): Unknown User (00:12:15): - Attachment: #3307 corrmeta > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/wsjung/corrmeta > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (01:48:21): - Attachment: #3308 Package Pirat > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/prostarproteomics/Pirat > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (02:47:37): - Attachment: #3309 SubcellularSpatialData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/DavisLaboratory/SubcellularSpatialData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-02-13

Unknown User (18:56:38): - Attachment: #3310 SpotSweeper > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/MicTott/SpotSweeper > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-02-14

Unknown User (11:09:04): Unknown User (11:09:05): Unknown User (11:09:06): Unknown User (11:09:08): Unknown User (11:09:09):

2024-02-15

Unknown User (07:19:52):

2024-02-18

Unknown User (10:42:25): - Attachment: #3311 hdxmsqc > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ococrook/hdxmsqc > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-02-19

Unknown User (21:06:44): - Attachment: #3312 CaMutQC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/likelet/CaMutQC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-02-21

Unknown User (15:51:19): - Attachment: #3313 BREW3R.r > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lldelisle/BREW3R.r > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-02-22

Unknown User (13:28:04): Unknown User (13:28:06): Unknown User (13:28:07): Unknown User (13:28:08): Unknown User (13:28:09): Unknown User (13:28:10): Unknown User (13:28:11): Unknown User (13:28:13): Unknown User (13:28:14):

2024-02-23

Unknown User (06:01:44): - Attachment: #3314 HybridExpress > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/almeidasilvaf/HybridExpress > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:42:01): - Attachment: #3315 BioGA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/danymukesha/BioGA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-02-24

Unknown User (11:20:26): - Attachment: #3316 tidysbml > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/veronicapaparozzi/tidysbml > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:20:28): Unknown User (13:24:39): - Attachment: #3317 tidysbml > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/veronicapaparozzi/tidysbml > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:24:41): Unknown User (13:38:02): - Attachment: #3318 tidysbml > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/veronicapaparozzi/tidysbml > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:38:04): Unknown User (13:49:15): - Attachment: #3319 tidysbml > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/veronicapaparozzi/tidysbml > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-02-26

Unknown User (08:02:36): - Attachment: #3320 treeclimbR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/csoneson/treeclimbR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:20:14): - Attachment: #3321 bettr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/federicomarini/bettr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:56:10): - Attachment: #3322 funomics package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/elisagdelope/funomics > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-02-28

Unknown User (19:16:52): - Attachment: #3323 simPIC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/sagrikachugh/simPIC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-02-29

Unknown User (07:59:31): Unknown User (07:59:32): Unknown User (09:09:49): - Attachment: #3324 GrafGen > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/wheelerb/GrafGen > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-03-04

Unknown User (08:12:20): Unknown User (08:12:21): Unknown User (08:12:22): Unknown User (08:12:23):

2024-03-06

Unknown User (01:34:39): - Attachment: #3325 Damsel > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Oshlack/Damsel > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-03-07

Unknown User (10:28:08): - Attachment: #3326 mulea > Dear Bioconductor Team, > > > > > With this issue we would like to submit the mulea package. mulea is a comprehensive overrepresentation and functional enrichment analyser R package which reads ontologies (gene and protein sets) in a standardised GMT (Gene Matrix Transposed) format. Please note, we have already submitted muleaData which is the data package for mulea: https://github.com/Bioconductor/Contributions/issues/3291 > > > > > Kind regards, > Tamás > > > > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ELTEbioinformatics/mulea > > > > > Please note, this repository has an upstream which is archived and will not be updated in the future. > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > > > > > BiocCheck::BiocCheck() returned the following: > > > > > > NOTE: Update R version dependency from 4.0.0 to 4.3.0. > > > I would rather not do this because then R CMD check will fail on oldrel-1 (https://github.com/ELTEbioinformatics/mulea/pull/24). The package does not require R 4.3.0. (I have turned off GitHub workflows for the submission process) > > > > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > > > > BiocCheck::BiocCheck() returned the following: > > > > > > NOTE: Cannot determine whether maintainer is subscribed to the Bioc-Devel mailing list (requires admin > credentials). Subscribe here: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > > I am registered to both the mailing list and the support forum. > > > > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:28:11): Unknown User (10:31:49): - Attachment: #3327 mulea > Dear Bioconductor Team, > > > > > With this issue we would like to submit the mulea package. mulea is a comprehensive overrepresentation and functional enrichment analyser R package which reads ontologies (gene and protein sets) in a standardised GMT (Gene Matrix Transposed) format. > > > > > Kind regards, > Tamás > > > > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ELTEbioinformatics/mulea > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:31:52): Unknown User (10:33:01): Unknown User (10:33:02): Unknown User (10:33:04):

2024-03-08

Unknown User (00:56:16): - Attachment: #3328 mulea > Dear Bioconductor Team, > > > > > With this issue we would like to submit the mulea package. mulea is a comprehensive overrepresentation and functional enrichment analyser R package which reads ontologies (gene and protein sets) in a standardised GMT (Gene Matrix Transposed) format. > > > > > Kind regards, > Tamás > > > > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ELTEbioinformatics/mulea > > > > > Please note, this repository has an upstream which is archived and will not be updated in the future. > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-03-11

Unknown User (07:16:08): Unknown User (12:06:36): - Attachment: #3329 MPAC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/pliu55/MPAC > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (21:02:17): - Attachment: #3330 chevreul and chevreuldata > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/whtns/chevreul/ > AdditionalPackage: https://github.com/whtns/chevreuldata > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (21:02:19): Unknown User (23:36:26): - Attachment: #3331 tidytof > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/keyes-timothy/tidytof > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-03-12

Unknown User (11:54:25): - Attachment: #3332 chevreuldata > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/whtns/chevreul/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-03-13

Unknown User (03:20:58): - Attachment: #3333 motifTestR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/smped/motifTestR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:16:53): - Attachment: #3334 UPDhmm > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/martasevilla/UPDhmm > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:16:56): Unknown User (04:40:11): - Attachment: #3335 UPDhmm > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/martasevilla/UPDhmm > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:36:27): - Attachment: #3336 scaeData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/AGImkeller/scaeData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:36:30): Unknown User (08:45:30): - Attachment: #3337 scaeData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/AGImkeller/scaeData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:45:32): Unknown User (09:04:32): - Attachment: #3338 scaeData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/AGImkeller/scaeData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:55:24): - Attachment: #3339 SingleCellAlleleExperiment > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/AGImkeller/SingleCellAlleleExperiment > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-03-14

Unknown User (09:51:10): - Attachment: #3340 SpatialExperimentIO > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: [https://github.com/estellad/SpatialExperimentIO](https://github.com/estellad/SpatialExperimentIO) > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming > > [10]: https://github.com/estellad/SpatialExperimentIO

Unknown User (09:51:12): Unknown User (09:53:30): - Attachment: #3341 SpatialExperimentIO > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: [https://github.com/estellad/SpatialExperimentIO](https://github.com/estellad/SpatialExperimentIO) > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming > > [10]: https://github.com/estellad/SpatialExperimentIO

Unknown User (09:53:32): Unknown User (09:55:20): - Attachment: #3342 SpatialExperimentIO > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: [https://github.com/estellad/SpatialExperimentIO](https://github.com/estellad/SpatialExperimentIO) > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:46:42):

2024-03-15

Unknown User (01:56:24): - Attachment: #3343 UCSC.utils > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Bioconductor/UCSC.utils > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:28:47): - Attachment: #3344 chai > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lodimk2/chai/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:28:49):

2024-03-16

Unknown User (14:49:20): - Attachment: #3345 tidyFlowCore > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/keyes-timothy/tidyFlowCore > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-03-17

Unknown User (12:53:47): - Attachment: #3346 smoothclust > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lmweber/smoothclust > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-03-18

Unknown User (05:24:50): - Attachment: #3347 New package omXplore > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/prostarproteomics/omXplore > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (06:11:34): - Attachment: #3348 iSEEfier > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/NajlaAbassi/iSEEfier > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:22:17): - Attachment: #3349 MAPFX > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/HsiaoChiLiao/MAPFX > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:59:51): - Attachment: #3350 CHAI > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lodimk2/chai > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:59:54): Unknown User (13:19:03): - Attachment: #3351 chai > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lodimk2/chai > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:15:35): Unknown User (14:15:57): Unknown User (14:16:19):

2024-03-19

Unknown User (20:51:51): - Attachment: #3352 gINTomics > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/angelovelle96/gINTomics > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-03-20

Unknown User (10:02:09): - Attachment: #3353 HoloFoodR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/EBI-Metagenomics/HoloFoodR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:09:32): - Attachment: #3354 New ExperimentHub package “JohnsonKinaseData” > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/fgeier/JohnsonKinaseData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:32:39): - Attachment: #3355 mosdef > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/imbeimainz/mosdef > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-03-21

Unknown User (04:57:15): - Attachment: #3356 ggtreeSpace > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/YuLab-SMU/ggtreeSpace > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:56:11): - Attachment: #3357 multistateQTL > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/dunstone-a/multistateQTL > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:48:01): - Attachment: #3358 GeDi > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/AnnekathrinSilvia/GeDi > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:48:04): Unknown User (11:53:10): Unknown User (12:00:01): - Attachment: #3359 GeDi > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/AnnekathrinSilvia/GeDi > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:27:17): - Attachment: #3360 smartid > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/DavisLaboratory/smartid > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:39:33): - Attachment: #3361 pwalign > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Bioconductor/pwalign > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-03-22

Unknown User (06:38:41): - Attachment: #3362 TENET3 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rhielab/TENET3.data > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (06:38:42): Unknown User (06:39:56): - Attachment: #3363 TENET3 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rhielab/TENET3.data > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (06:39:58): Unknown User (13:13:58): - Attachment: #3364 LegATo > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/aubreyodom/LegATo > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:14:00): Unknown User (13:17:41): - Attachment: #3365 LegATo > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/wejlab/LegATo > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:17:44): Unknown User (13:38:30): - Attachment: #3366 rBLAST > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mhahsler/rBLAST > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x^ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > > > > ^ Notes to the reviewer: > - The warnings about long lines are due to long lines in man pages created by > the formatter in roxygen. I have no control over this. > - One function is > 50 lines. Breaking it into several functions would not improve the code. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:03:07): Unknown User (14:03:08): Unknown User (14:03:09): Unknown User (14:03:10): Unknown User (14:03:11): Unknown User (14:03:12): Unknown User (14:03:14): Unknown User (18:38:16): - Attachment: #3367 bugphyzz > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/waldronlab/bugphyzz > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:44:57): - Attachment: #3368 SpatialExperimentIO > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/estellad/SpatialExperimentIO/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:44:59): Unknown User (20:49:28): - Attachment: #3369 SpatialExperimentIO > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/estellad/SpatialExperimentIO > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:49:29): Unknown User (20:53:09): - Attachment: #3370 SpatialExperimentIO > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/estellad/SpatialExperimentIO > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:15:14): - Attachment: #3371 pathwrap > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Kannapolis-Bioinformatics/pathwrap > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:15:16): Unknown User (22:22:00): - Attachment: #3372 pathwrap > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Kannapolis-Bioinformatics/pathwrap > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-03-23

Unknown User (00:28:19): - Attachment: #3373 AnVILBase > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Bioconductor/AnVILBase > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (00:28:21): Unknown User (00:59:12): - Attachment: #3374 AnVILBase > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Bioconductor/AnVILBase > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-03-26

Unknown User (05:45:55): - Attachment: #3375 IlluminaHumanMethylationEPICv2manifest > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jokergoo/IlluminaHumanMethylationEPICv2manifest > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:45:57): Unknown User (05:46:44): - Attachment: #3376 IlluminaHumanMethylationEPICv2anno.20a1.hg38 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jokergoo/IlluminaHumanMethylationEPICv2anno.20a1.hg38 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:46:45): Unknown User (09:59:01): - Attachment: #3377 HicAggR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CuvierLab/HicAggR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:59:04): Unknown User (12:11:31): - Attachment: #3378 HicAggR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CuvierLab/HicAggR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:11:34): Unknown User (12:26:36): Unknown User (13:00:23): - Attachment: #3379 smoppix > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/sthawinke/smoppix > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-03-27

Unknown User (09:26:10): Unknown User (09:26:12): Unknown User (09:26:13): Unknown User (09:26:14): Unknown User (09:26:15): Unknown User (09:26:16): Unknown User (09:26:17): Unknown User (09:32:08): Unknown User (10:39:43): - Attachment: #3380 broadSeq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/dasroy/broadSeq > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:39:45): Unknown User (11:10:26): - Attachment: #3381 broadSeq resubmission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/dasroy/broadSeq > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-03-28

Unknown User (12:21:18): Unknown User (12:21:19):

2024-03-29

Unknown User (05:16:59): - Attachment: #3382 Add new package: PolySTest > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/computproteomics/PolySTest > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:17:00): Unknown User (05:45:51): - Attachment: #3383 Add PolySTest > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/computproteomics/PolySTest > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:48:19): - Attachment: #3384 scToppR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BioinformaticsMUSC/scToppR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:48:20):

2024-04-02

Unknown User (13:35:38): Unknown User (13:35:39): Unknown User (13:35:40): Unknown User (13:35:40): Unknown User (13:35:42): Unknown User (22:52:48): - Attachment: #3385 sceptredata, ondisc, and sceptre > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Katsevich-Lab/sceptredata > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:52:50): Unknown User (23:14:21): - Attachment: #3386 sceptredata, ondisc, and sceptre > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Katsevich-Lab/sceptredata > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (23:14:23):

2024-04-03

Unknown User (17:30:52): - Attachment: #3387 squallms > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/wkumler/squallms > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of mass-spectrometry data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-04-04

Unknown User (10:13:17): Unknown User (10:13:18): Unknown User (10:13:19): Unknown User (10:13:20):

2024-04-05

Unknown User (20:23:44): - Attachment: #3388 Pull Request Forget passphrase > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/SGCP > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:23:46):

2024-04-09

Unknown User (13:05:58): - Attachment: #3389 scToppR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BioinformaticsMUSC/scToppR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:06:01): Unknown User (13:15:25): - Attachment: #3390 scToppR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/BioinformaticsMUSC/scToppR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:15:28):

2024-04-10

Unknown User (09:08:56): - Attachment: #3391 KoinaR - R package to interface with Koina web service > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/wilhelm-lab/koinar > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic proteomics data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:08:58): Unknown User (09:15:31): - Attachment: #3392 KoinaR - R package to interface with Koina web service > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/wilhelm-lab/koinar > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic proteomics data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-04-11

Unknown User (12:45:25):

2024-04-12

Unknown User (17:03:47): - Attachment: #3393 DNEA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > -Note: The package is currently stored on the Lab github but I do the maintenance and developement as a member of said lab. My github profile is chrispatsalis. > > > > > • Repository: https://github.com/Karnovsky-Lab/DNEA/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-04-16

Unknown User (08:28:25): Unknown User (08:28:26): Unknown User (08:28:27): Unknown User (08:28:29): Unknown User (08:28:30): Unknown User (08:28:31): Arshi Arora (13:31:38): > @Arshi Arora has joined the channel

Unknown User (22:18:20): - Attachment: #3394 ADAPT (Analysis of Microbiome Differential Abundance by Pooling Tobit Models) > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mkbwang/ADAPT > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-04-19

Unknown User (09:06:13):

2024-04-22

Unknown User (13:44:39): - Attachment: #3395 MS2extract submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CooperstoneLab/MS2extract > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:44:42): Unknown User (13:48:57): - Attachment: #3396 MS2extract > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CooperstoneLab/MS2extract > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:48:59): Unknown User (14:03:54): - Attachment: #3397 MS2extract > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CooperstoneLab/MS2extract > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:03:57): Unknown User (14:18:43): Unknown User (14:18:44): Unknown User (14:18:45): Unknown User (14:18:47): Unknown User (14:19:04): - Attachment: #3398 MS2extract > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CooperstoneLab/MS2extract > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-04-23

Unknown User (18:19:53): - Attachment: #3399 MultimodalGraphics for Visualization of Multimodal Datasets > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/famanalytics0/MultiModalGraphics > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-04-24

Unknown User (06:06:18): - Attachment: #3400 seahtrue > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/vcjdeboer/seahtrue > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (06:06:20): Unknown User (06:29:28): - Attachment: #3401 seahtrue > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/vcjdeboer/seahtrue > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:36:15):

2024-04-25

Unknown User (09:07:43): Unknown User (09:07:44): Unknown User (09:07:45): Unknown User (09:07:46): Unknown User (09:07:47): Unknown User (09:07:48): Unknown User (09:07:49): Unknown User (09:07:50):

2024-04-26

Francesc Català-Moll (09:36:36): > @Francesc Català-Moll has joined the channel

Unknown User (12:16:54): Unknown User (12:16:55):

2024-04-29

Unknown User (16:24:39): - Attachment: #3402 Differentially Expressed Heterogeneous Over-dispersion Gene test > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/arlinashen/DEHOGT > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:24:42): Unknown User (16:26:40): - Attachment: #3403 Differentially Expressed Heterogeneous OverDispersion Gene Testing > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/arlinashen/DEHOGT > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:26:42): Unknown User (16:29:09): - Attachment: #3404 Differentially Expressed Heterogeneous OverDispersion Gene Test > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/arlinashen/DEHOGT > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:29:11): Unknown User (16:31:15): - Attachment: #3405 Differentially Expressed Heterogeneous Overdispersion Gene Testing > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/arlinashen/DEHOGT > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:31:17): Unknown User (18:01:42): - Attachment: #3406 Differentially Expressed Heterogenous OverDispersion Gene Test > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/arlinashen/DEHOGT > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:01:44): Unknown User (18:06:24): - Attachment: #3407 Differentially Expressed Heterogeneous OverDispersion Gene Test > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/arlinashen/DEHOGT > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:06:26): Unknown User (18:11:24): - Attachment: #3408 Differentially Expressed Heterogeneous OverDispersion Gene Test > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/arlinashen/DEHOGT > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-04-30

Unknown User (23:54:43): Unknown User (23:55:22): - Attachment: #3409 Differentially Expressed Heterogeneous OverDispersion Gene Test > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/arlinashen/DEHOGT > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (23:55:24): Unknown User (23:55:44):

2024-05-01

Unknown User (16:48:16): Unknown User (16:52:50): - Attachment: #3410 Differentially Expressed Heterogeneous Gene Test > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ahshen26/DEHOGT > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:52:52): Unknown User (16:57:50): - Attachment: #3411 Differentially Expressed Heterogeneous Gene Testing > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ahshen26/DEHOGT > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:57:53): Unknown User (16:59:44): Unknown User (17:02:31):

2024-05-08

Unknown User (04:56:06): - Attachment: #3412 SCIntRuler > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yuelyu21/SCIntRuler > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:56:09): Unknown User (10:40:56): - Attachment: #3413 crupR submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/akbariomgba/crupR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-05-09

Unknown User (06:56:22): Unknown User (15:41:07): - Attachment: #3414 request to submit a new package: CleanUpRNAseq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/haibol2016/CleanUpRNAseq > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:41:10):

2024-05-12

Unknown User (11:34:57): - Attachment: #3415 PepSetTest > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/JmWangBio/PepSetTest > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:35:00):

2024-05-13

Unknown User (07:36:54): Unknown User (10:13:09): - Attachment: #3416 dominoSignal > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/FertigLab/dominoSignal > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (19:03:46): - Attachment: #3417 PepSetTest > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/JmWangBio/PepSetTest > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-05-14

Unknown User (17:11:33): - Attachment: #3418 mapper > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/haihuilab/mapper > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:11:35): Unknown User (18:11:08): - Attachment: #3419 mapper > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/haihuilab/mapper > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:33:49): - Attachment: #3420 mapper > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/haihuilab/mapper > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:33:51):

2024-05-15

Unknown User (01:04:42): - Attachment: #3421 SpatialDeX > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/wang-lab/SpatialDeX > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (01:04:45): Unknown User (22:37:34): - Attachment: #3422 SpatialDeX > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/wang-lab/SpatialDeX > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-05-16

Unknown User (04:52:37): - Attachment: #3423 New package submission: rhinotypeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/omicscodeathon/rhinotypeR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:52:38): Unknown User (16:19:49): - Attachment: #3424 scDotPlot > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ben-laufer/scDotPlot > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-05-17

Unknown User (12:14:12): - Attachment: #3425 mapper > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/haihuilab/mapper > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:14:15): Unknown User (12:29:13): Unknown User (12:30:02): Unknown User (12:30:03):

2024-05-20

Unknown User (00:38:32): - Attachment: #3426 StabMap > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/StabMap > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:00:38): - Attachment: #3427 SPADE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/thecailab/SPADE > > > > > SPADE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:00:41): Unknown User (16:03:02): - Attachment: #3428 SPADE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/thecailab/SPADE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:03:04): Unknown User (16:07:03): - Attachment: #3429 SPADE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/thecailab/SPADE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:07:05): Unknown User (16:10:06): - Attachment: #3430 SPADE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/thecailab/SPADE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:10:09): Unknown User (16:14:22): - Attachment: #3431 SPADE submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/thecailab/SPADE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:14:24): Unknown User (16:16:03): - Attachment: #3432 SPADE submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/thecailab/SPADE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:16:06): Unknown User (16:23:01): - Attachment: #3433 SPADE submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/thecailab/SPADE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:23:03): Unknown User (16:36:26): - Attachment: #3434 SPADE submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/thecailab/SPADE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-05-21

Unknown User (13:26:14): - Attachment: #3435 ggseqalign > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://gitlab.com/nmbu.no/ipv/lim-rossmann/ggseqalign > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:26:16): Unknown User (13:58:41): - Attachment: #3436 ggseqalign > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/simeross/ggseqalign > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:58:44): Unknown User (14:02:09): - Attachment: #3437 ggseqalign > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/simeross/ggseqalign > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-05-22

Unknown User (08:40:41): - Attachment: #3438 PRONE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lisiarend/PRONE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:40:43): Unknown User (08:56:44): - Attachment: #3439 PRONE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lisiarend/PRONE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:56:46): Unknown User (10:10:13): - Attachment: #3440 PRONE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lisiarend/PRONE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-05-23

Unknown User (10:02:42): - Attachment: #3441 clrng: Parallel Random Number Generation on GPU in R > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ruoyongxu/clrng > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:02:44): Unknown User (22:04:58): - Attachment: #3442 Please help submit my CleanUpRNAseq package to Bioconductor > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/haibol2016/CleanUpRNAseq > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ X] The ‘devel’ branch for new packages and features. > • [ X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-05-27

Unknown User (06:48:51):

2024-05-29

Unknown User (09:36:46): - Attachment: #3443 submitting package CatsCradle > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/AnnaLaddach/CatsCradle > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:36:48): Unknown User (12:17:47): - Attachment: #3444 submitting package CatsCradle > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/AnnaLaddach/CatsCradle > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:17:50): Unknown User (23:12:07): - Attachment: #3445 spaceMarker > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/phipsonlab/spaceMarker > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-05-31

Unknown User (12:10:35): - Attachment: #3446 immunogenViewer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/kathiwaury/immunogenViewer > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-06-03

Unknown User (10:12:30): - Attachment: #3447 submitting a new package, CatsCradle > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/AnnaLaddach/CatsCradle > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:12:33): Unknown User (10:13:40): Unknown User (14:40:47): - Attachment: #3448 SEraster > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/JEFworks-Lab/SEraster > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (23:50:59): - Attachment: #3449 Bioconductor submission of scDiagnostics: diagnostic functions to assess the quality of cell type annotations in single-cell RNA-seq data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ccb-hms/scDiagnostics > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-06-04

Unknown User (03:04:29): - Attachment: #3450 iSEEtree > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/microbiome/iSEEtree > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (03:04:32): Unknown User (03:22:17): - Attachment: #3451 iSEEtree > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/microbiome/iSEEtree > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:35:52): - Attachment: #3452 submitting new package CatsCradle > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/annaladdach/CatsCradle > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-06-07

Unknown User (11:50:45): Unknown User (11:50:46): Unknown User (11:50:47): Unknown User (11:50:48): Unknown User (11:50:49): Unknown User (11:50:50):

2024-06-09

Unknown User (12:23:10): - Attachment: #3453 DuplexDiscovereR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository:https://github.com/Egors01/DuplexDiscovereR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-06-10

Unknown User (06:49:12): - Attachment: #3454 rhinotypeR package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > Repository: https://github.com/omicscodeathon/rhinotypeR > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:12:24): - Attachment: #3455 vmrseq > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/nshen7/vmrseq > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-06-12

Unknown User (00:32:05): - Attachment: #3456 loxcodeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tomsergeweber/loxcodeR_data > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (00:32:07):

2024-06-14

Unknown User (09:15:40): Unknown User (09:15:41): Unknown User (09:15:42):

2024-06-15

Unknown User (02:00:40): - Attachment: #3457 eoPredData > This is an experimentHub data package. Also pinging author @iciarfernandez > > > > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/wvictor14/eopreddata > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (02:00:41): Unknown User (11:38:28): - Attachment: #3458 eoPredData > This is an experimentHub data package. Also pinging author @iciarfernandez > > > > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/wvictor14/eoPredData > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-06-17

Unknown User (17:40:49): - Attachment: #3459 mspms > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/baynec2/mspms/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:40:52): Unknown User (18:13:53): - Attachment: #3460 mspms > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/baynec2/mspms > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:09:51): - Attachment: #3461 loxcodeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tomsergeweber/loxcodeR/tree/main > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-06-19

Unknown User (09:48:31): - Attachment: #3462 Polytect: an automatic clustering and labeling method for multi-color digital PCR data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.ugent.be/DIGPCR/Polytect > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:48:34): Unknown User (10:19:52): - Attachment: #3463 Polytect: an automatic clustering and labeling method for multi-color digital PCR data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/emmachenlingo/Polytect > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:19:54): Unknown User (12:03:38): - Attachment: #3464 Polytect: an automatic clustering and labeling method for multi-color digital PCR data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/emmachenlingo/Polytect > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-06-20

Unknown User (07:07:44): - Attachment: #3465 eheat > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Yunuuuu/eheat > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:44:25): - Attachment: #3466 GenomicLLM > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Kohze/GenomicLLM > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:44:26):

2024-06-23

Unknown User (14:32:41): - Attachment: #3467 Fixing the bug in SGCP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:32:43):

2024-06-24

Unknown User (07:52:49): - Attachment: #3468 EnrichDO > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/liangcheng-hrbmu/EnrichDO > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:04:58): - Attachment: #3469 batchCorr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/MetaboComp/batchCorr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:53:22): Unknown User (20:04:52): Unknown User (20:05:44):

2024-06-25

Unknown User (09:46:23):

2024-06-26

Unknown User (08:20:59): Unknown User (08:21:03):

2024-06-27

Unknown User (16:59:57): - Attachment: #3470 CARDspa > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/YMa-lab/CARDspa > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-06-28

Unknown User (08:03:25): Unknown User (08:07:28): Unknown User (11:12:41): - Attachment: #3471 LoriTestPkg > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lshep/LoriTestPkg > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:12:43): Unknown User (11:28:16): - Attachment: #3472 LoriTestPkg > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lshep/LoriTestPkg > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:34:17): - Attachment: #3473 TENET.AnnotationHub > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rhielab/TENET.AnnotationHub > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-07-08

Unknown User (09:46:24): - Attachment: #3474 Differentially Expressed Heterogeneous Gene Test > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ahshen26/DEHOGT > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:46:25): Unknown User (11:26:38): - Attachment: #3475 RFLOMICS > Dear Bioconductor team, > > > > > • Repository: https://github.com/RFLOMICS/RFLOMICS.git > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:26:40): Unknown User (11:32:01): - Attachment: #3476 RFLOMICS > Dear Bioconductor team, > > > > > • Repository: https://github.com/RFLOMICS/RFLOMICS > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:32:03): Unknown User (12:00:37): - Attachment: #3477 RFLOMICS > Dear Bioconductor team, > > > > > • Repository: https://github.com/RFLOMICS/RFLOMICS > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-07-10

Unknown User (08:50:04): - Attachment: #3478 biotidy > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Yunuuuu/biotidy > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:03:00): - Attachment: #3479 staRgate > Hello Bioconductor team, > I am submitting my R package {staRgate} in consideration for Bioconductor release. > > > > > Thank you for your time and consideration! > > > > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/leejasme/staRgate > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:03:03): Unknown User (16:48:33): - Attachment: #3480 g3viz > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/G3viz/g3viz- > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:48:35): Unknown User (17:17:30): - Attachment: #3481 g3viz > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ruiningzhu/g3viz > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:17:32): Unknown User (17:21:24): - Attachment: #3482 g3viz > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ruiningzhu/g3viz/tree/master > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:21:25):

2024-07-11

Unknown User (13:08:02): - Attachment: #3483 MotifPeeker > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/neurogenomics/MotifPeeker > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:41:56): - Attachment: #3484 staRgate > Hello Bioconductor team, > I am submitting my R package {staRgate} in consideration for Bioconductor release. > > > > > Thank you for your time and consideration! > > > > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/leejasme/staRgate > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:41:58): Unknown User (16:51:12): - Attachment: #3485 staRgate > Hello Bioconductor team, > I am submitting my R package {staRgate} in consideration for Bioconductor release. > > > > > Thank you for your time and consideration! > > > > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/leejasme/staRgate > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:09:07): - Attachment: #3486 SplineDV > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Xenon8778/SplineDV > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:09:08):

2024-07-12

Unknown User (13:02:59): - Attachment: #3487 SplineDV > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Xenon8778/SplineDV > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:03:01): Unknown User (13:18:52): - Attachment: #3488 SplineDV > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Xenon8778/SplineDV > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:18:54): Unknown User (13:28:51): - Attachment: #3489 SplineDV > Hello Bioconductor team, > I am submitting my R package {SplineDV} for consideration for Bioconductor release. > > > > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Xenon8778/SplineDV > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-07-16

Unknown User (08:04:21): Unknown User (09:23:20): Unknown User (09:23:21): Unknown User (09:23:23):

2024-07-18

Unknown User (15:15:10): - Attachment: #3490 chevreuldata > This is an experimentHub data package. Also pinging author @Bavanaa. This is a dependency for recently submitted package chevreul https://github.com/Bioconductor/Contributions/issues/3332 > > > > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/whtns/chevreuldata > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:15:12): Unknown User (15:16:53): - Attachment: #3491 chevreuldata > This is an experimentHub data package. Also pinging author @Bavanaa. This is a dependency for recently submitted package chevreul #3332 > > > > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > > Repository: https://github.com/whtns/chevreuldata > > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > > [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > [x ] I have read the Bioconductor [Package Submission](https://bioconductor.org/developers/package-submission/) > instructions. My package is consistent with the Bioconductor > [Package Guidelines](https://contributions.bioconductor.org/). > > [x ] I understand Bioconductor [Package Naming Policy](https://bioconductor.org/developers/package-submission/#naming) and acknowledge > Bioconductor may retain use of package name. > > [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the [support site](https://support.bioconductor.org/) for issues that users may > have, subscribing to the [bioc-devel](https://stat.ethz.ch/mailman/listinfo/bioc-devel) mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > [x ] I am familiar with the [Bioconductor code of conduct](https://bioconductor.org/about/code-of-conduct/) and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > > [ x] The 'devel' branch for new packages and features. > [ x] The stable 'release' branch, made available every six > months, for bug fixes. > [ x] Bioconductor version control using [Git](http://bioconductor.org/developers/how-to/git/) > (optionally [via GitHub](http://bioconductor.org/developers/how-to/git/sync-existing-repositories/)). > > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up.

Unknown User (15:37:22): - Attachment: #3492 assorthead > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/LTLA/assorthead > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:37:23): Unknown User (15:41:02): - Attachment: #3493 assorthead > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/LTLA/assorthead > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:41:04):

2024-07-19

Unknown User (03:39:29): - Attachment: #3494 assorthead > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/LTLA/assorthead > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:58:05): - Attachment: #3495 immApex > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ncborcherding/immApex > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:58:07):

2024-07-20

Unknown User (14:20:41): - Attachment: #3496 immApex > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ncborcherding/immApex > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:20:44):

2024-07-22

Unknown User (09:02:21): - Attachment: #3497 immApex > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ncborcherding/immApex > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-07-23

Unknown User (10:01:18): - Attachment: #3498 HiCParser > This package is a parser to import HiC data into R, from several formats. Most of functions are extracted from our Bioconductor Package HiCDOC (already published). But this package can be cumbersome to install. Our goal is to split the actual HiCDOC package in two : one package to parse the data (a “light” package, that could be used in other packages to import Hi-C data) and a future HiCDOC package, without the definitions of parser functions. > > > > > > > > • Repository: https://github.com/emaigne/HiCParser > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-07-26

Unknown User (01:05:40): - Attachment: #3499 EnsemblGenomes > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/js2264/EnsemblGenomes > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:08:04): - Attachment: #3500 MSstatsBioNet > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Vitek-Lab/MSstatsBioNet > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-07-29

Unknown User (09:16:10): Unknown User (14:52:32): - Attachment: #3501 visiumStitched > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/LieberInstitute/visiumStitched > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-07-30

Unknown User (08:01:36):

2024-08-01

Unknown User (09:49:02): - Attachment: #3502 scoup: Simulate Codon Sequences with Darwinian Selection Incorporated as an Ornstein-Uhlenbeck Process > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/thsadiq/scoup > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-08-05

Unknown User (10:03:56): Unknown User (10:03:57): Unknown User (10:03:58): Unknown User (10:03:59): Unknown User (10:04:00): Unknown User (10:04:01): Unknown User (10:07:32):

2024-08-07

Unknown User (13:24:03): - Attachment: #3503 DeconvoBuddies > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/LieberInstitute/DeconvoBuddies > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-08-09

Unknown User (09:32:18):

2024-08-11

Unknown User (09:43:43): - Attachment: #3504 org.Qsuber.eg.db > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/nmauri/bioconductor1_org.qsuber.eg.db > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:43:45): Unknown User (12:33:34): - Attachment: #3505 org.Qsuber.eg.db > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:33:36): Unknown User (12:34:49): - Attachment: #3506 org.Qsuber.eg.db > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/nmauri/org.qsuber.eg.db > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:34:51): Unknown User (12:37:17): - Attachment: #3507 org.qsuber.eg.db > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/nmauri/org.qsuber.eg.db > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:37:19): Unknown User (12:39:06): - Attachment: #3508 org.Qsuber.eg.db > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/nmauri/org.Qsuber.eg.db > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:39:08): Unknown User (13:13:05): - Attachment: #3509 org.Qsuber.eg.db > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/nmauri/org.Qsuber.eg.db > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:13:08): Unknown User (16:54:10): - Attachment: #3510 org.Qsuber.eg.db > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/nmauri/org.Qsuber.eg.db > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:54:12): Unknown User (16:55:22): - Attachment: #3511 org.Qsuber.eg.db > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/nmauri/org.Qsuber.eg.db > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:55:25): Unknown User (17:02:38): - Attachment: #3512 org.Qsuber.eg.db > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/nmauri/org.Qsuber.eg.db > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:02:41): Unknown User (17:03:53): - Attachment: #3513 org.Qsuber.eg.db > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/nmauri/org.Qsuber.eg.db > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:03:55):

2024-08-12

Unknown User (08:12:59): Unknown User (08:13:27): Unknown User (18:44:13): - Attachment: #3514 CaseControlAF > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/wolffha/CaseControlAF/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-08-13

Unknown User (03:37:39): - Attachment: #3515 scQTLtools > Hello Bioconductor team, > I am submitting my R package {scQTLtools} for consideration for Bioconductor release. > > > > > • Repository: https://github.com/XFWuCN/scQTLtools > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-08-15

Unknown User (08:35:29): Unknown User (08:38:15): Unknown User (08:39:57):

2024-08-16

Unknown User (19:43:10): - Attachment: #3516 CPSM > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/hks5august/CPSM > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (19:43:12): Unknown User (19:53:12): - Attachment: #3517 CPSM > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/hks5august/CPSM > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (19:53:14): Unknown User (20:09:17): - Attachment: #3518 CPSM > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/hks5august/CPSM > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-08-20

Unknown User (00:30:03): - Attachment: #3519 XAItest > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/GhislainFievet/XAItest > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:36:36): - Attachment: #3520 Differentially Expressed Heterogeneous Overdispersion Gene Testing > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ahshen26/DEHOGT > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:36:39): Unknown User (11:40:55): - Attachment: #3521 > The code in your repo does not form an R package. Please see https://contributions.bioconductor.org/ … reopen when you have a package that can be installed and that passes R CMD check. Thank you! > > > The code in your repo does not form an R package. Please see https://contributions.bioconductor.org/ ... reopen when you have a package that can be installed and that passes R CMD check. Thank you! > > > > > > Hi I have adjusted the package so that it passes R CMD check. Could you reopen this for me? I tried to re-submit my package but it says that it is currently linked to this issue. > > > > > Originally posted by @ahshen26 in https://github.com/Bioconductor/Contributions/issues/3408#issuecomment-2299164059

Unknown User (11:40:58): Unknown User (11:43:08): Unknown User (13:41:15): - Attachment: #3522 scToppR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/bryanwgranger/scToppR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:41:18): Unknown User (13:44:29): - Attachment: #3523 scToppR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/bryanwgranger/scToppR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:34:50): - Attachment: #3524 LegATo > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/wejlab/LegATo > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-08-21

Unknown User (07:22:56): - Attachment: #3525 SpectraQL package to support MassQL on Bioconductor’s mass spectrometry objects > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/RforMassSpectrometry/SpectraQL > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:53:48):

2024-08-23

Unknown User (20:18:20): - Attachment: #3526 TMSig > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/EMSL-Computing/TMSig > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-08-26

Unknown User (10:55:16): - Attachment: #3527 bedbaser > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/waldronlab/bedbaser > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-08-28

Unknown User (14:33:45): - Attachment: #3528 mvlearnR_package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/lasandrall/mvlearnR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:33:47):

2024-08-29

Unknown User (11:13:48): - Attachment: #3529 Polytect: an automatic clustering and labeling method for multi-color digital PCR data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/emmachenlingo/Polytect > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:13:51): Unknown User (11:19:40): Unknown User (11:39:46): - Attachment: #3530 HuBMAPR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/christinehou11/HuBMAPR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:39:49): Unknown User (11:51:28): - Attachment: #3531 HuBMAPR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/yourusername/yourpackagename > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:51:29): Unknown User (11:52:54): - Attachment: #3532 HuBMAPR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/christinehou11/HuBMAPR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-08-30

Unknown User (08:23:25): - Attachment: #3533 SpatialExperimentIO > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/estellad/SpatialExperimentIO > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:23:28):

2024-09-01

Unknown User (16:13:39): - Attachment: #3534 A package for 3D plot of epigenetic data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jianhong/geomeTriD > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-09-03

Unknown User (08:46:20): Unknown User (11:59:36): Unknown User (11:59:37): Unknown User (11:59:38):

2024-09-04

Unknown User (04:44:21): Unknown User (08:27:02):

2024-09-09

Unknown User (23:33:59): - Attachment: #3535 scrapper > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/libscran/scrapper > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (23:34:00): Unknown User (23:39:28): - Attachment: #3536 scrapper > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/libscran/scrapper > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-09-10

Unknown User (03:15:19): - Attachment: #3537 jazzPanda > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/phipsonlab/jazzPanda > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (03:15:22): Unknown User (03:22:11): - Attachment: #3538 jazzPanda > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/phipsonlab/jazzPanda > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:17:56): - Attachment: #3539 xCell2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/AlmogAngel/xCell2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:17:59): Unknown User (04:31:05): - Attachment: #3540 xCell2 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/AlmogAngel/xCell2 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-09-11

Unknown User (02:38:10): - Attachment: #3541 Spectra backend to support import of data from MetaboLights > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rformassspectrometry/MsBackendMetaboLights > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:18:11): - Attachment: #3542 xenLite > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/vjcitn/xenLite > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:46:06): - Attachment: #3543 EpipwR.data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jbarth216/EpipwR.data > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-09-12

Unknown User (14:07:53): - Attachment: #3544 spatialSimGP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/kinnaryshah/spatialSimGP > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-09-15

Unknown User (11:02:21): - Attachment: #3545 OmicsMLRepoR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/shbrief/OmicsMLRepoR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:02:22): Unknown User (11:03:30): - Attachment: #3546 OmicsMLRepoR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/shbrief/OmicsMLRepoR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:03:32): Unknown User (11:06:53): - Attachment: #3547 OmicsMLRepoR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/shbrief/OmicsMLRepoR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:06:55): Unknown User (11:17:59): - Attachment: #3548 OmicsMLRepoR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/shbrief/OmicsMLRepoR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:18:02): Unknown User (14:51:11): - Attachment: #3549 OmicsMLRepoR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/shbrief/OmicsMLRepoR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:51:13): Unknown User (14:54:59): - Attachment: #3550 OmicsMLRepoR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository:https://github.com/shbrief/OmicsMLRepoR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:55:01): Unknown User (14:58:43): - Attachment: #3551 OmicsMLRepoR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/shbrief/OmicsMLRepoR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-09-16

Unknown User (09:01:59): - Attachment: #3552 BulkSignalR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ZheFrench/BulkSignalR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ xx] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:02:01): Unknown User (11:42:46): - Attachment: #3553 BulkSignalR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ZheFrench/BulkSignalR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:42:50): Unknown User (11:50:05): - Attachment: #3554 BulkSignalR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ZheFrench/BulkSignalR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (19:20:21): - Attachment: #3555 DFplyr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jonocarroll/DFplyr > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (23:04:15): - Attachment: #3556 PloidyPeaks > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/MicroStatsLab/PloidyPeaks > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (23:04:17): Unknown User (23:06:56): - Attachment: #3557 PloidyPeaks > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/MicroStatsLab/PloidyPeaks > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (23:06:58): Unknown User (23:08:56): - Attachment: #3558 PloidyPeaks > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/MicroStatsLab/PloidyPeaks > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (23:08:58):

2024-09-17

Unknown User (04:40:24): - Attachment: #3559 BulkSignalR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ZheFrench/BulkSignalR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (04:40:27): Unknown User (07:10:57): - Attachment: #3560 MOSClip > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/CaluraLab/MOSClip > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:31:09): Unknown User (08:32:55): - Attachment: #3561 BulkSignalR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ZheFrench/BulkSignalR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:32:58): Unknown User (08:48:26): - Attachment: #3562 BulkSignalR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ZheFrench/BulkSignalR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:48:29): Unknown User (09:27:48): - Attachment: #3563 MetaboDynamics: initial submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/KatjaDanielzik/MetaboDynamics > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:27:50): Unknown User (09:32:22): - Attachment: #3564 MetaboDynamics: initial submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/KatjaDanielzik/MetaboDynamics > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:32:26): Unknown User (09:48:39): - Attachment: #3565 MetaboDynamics: intital submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/KatjaDanielzik/MetaboDynamics > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:24:59): Unknown User (12:41:44): Unknown User (18:33:51): - Attachment: #3566 PloidyPeaks > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/MicroStatsLab/PloidyPeaks > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:33:54):

2024-09-18

Unknown User (18:39:13): - Attachment: #3567 PloidyPeaks > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/MicroStatsLab/PloidyPeaks > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-09-19

Unknown User (02:24:04): - Attachment: #3568 SpatialFeatures > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/SpatialFeatures > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (02:24:06): Unknown User (02:39:32): - Attachment: #3569 SpatialFeatures > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/SpatialFeatures > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (02:45:20): - Attachment: #3570 wSIR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/wSIR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:29:10): - Attachment: #3571 clustSIGNAL > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/SydneyBioX/clustSIGNAL > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:38:24): - Attachment: #3572 biocmask > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jtlandis/biocmask > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:42:05): - Attachment: #3573 oob > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/DimitriMeistermann/oob > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:42:06): Unknown User (15:47:42): - Attachment: #3574 oob > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/DimitriMeistermann/oob > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:53:11): - Attachment: #3575 Submission of ProteinGymR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ccb-hms/ProteinGymR/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-09-20

Unknown User (00:28:05): - Attachment: #3576 IdentifiHR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/DavidsonGroup/IdentifiHR.git > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (00:28:07): Unknown User (00:30:32): - Attachment: #3577 IdentifiHR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/DavidsonGroup/IdentifiHR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (00:30:34): Unknown User (00:33:24): - Attachment: #3578 IdentifiHR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/DavidsonGroup/IdentifiHR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (00:33:26): Unknown User (01:01:15): - Attachment: #3579 IdentifiHR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/DavidsonGroup/IdentifiHR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (03:28:10): - Attachment: #3580 SpaNorm > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/bhuvad/SpaNorm > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:30:44): - Attachment: #3581 MetMashR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/computational-metabolomics/MetMashR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:30:47): Unknown User (08:42:46): - Attachment: #3582 MetMashR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/computational-metabolomics/MetMashR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:20:22): - Attachment: #3583 sosta > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/sgunz/sosta > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:20:24): Unknown User (09:39:35): - Attachment: #3584 sosta > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/sgunz/sosta > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:43:21): - Attachment: #3585 spatialFDA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mjemons/spatialFDA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:17:42): - Attachment: #3586 bamSliceR: Slicing and Tallied BAMs from GDC and local for Variants Analysis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/trichelab/bamSliceR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:17:45): Unknown User (18:32:47): - Attachment: #3587 bamSliceR: Slicing and Tallied BAMs from GDC and local for Variants Analysis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/trichelab/bamSliceR > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-09-24

Unknown User (11:31:48): Unknown User (11:31:48): Unknown User (15:52:35): Unknown User (23:03:25): - Attachment: #3588 ADM > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Seven595/ADMPackage > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (23:03:27): Unknown User (23:12:47): - Attachment: #3589 ADM > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Seven595/ADM > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-09-25

Unknown User (06:33:43): - Attachment: #3590 TENET.ExperimentHub > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rhielab/TENET.ExperimentHub > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-09-26

Unknown User (09:50:42): - Attachment: #3591 SVbyEye > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/daewoooo/SVbyEye > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-09-27

Unknown User (09:59:49): Unknown User (11:39:50): - Attachment: #3592 ReducedExperiment > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jackgisby/ReducedExperiment > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-09-29

Unknown User (20:41:39): - Attachment: #3593 scLANE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jr-leary7/scLANE > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:41:40):

2024-10-01

Unknown User (12:50:11): Unknown User (12:50:12): Unknown User (12:50:13): Unknown User (12:50:14): Unknown User (20:47:28):

2024-10-02

Unknown User (07:05:27): Unknown User (15:08:50): Unknown User (15:09:19): Eva Hamrud (19:07:24): > @Eva Hamrud has joined the channel

2024-10-05

Unknown User (03:06:36): - Attachment: #3594 TENET > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rhielab/TENET > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-10-07

Unknown User (07:26:13): Unknown User (07:26:14): Unknown User (07:26:15): Unknown User (07:26:16):

2024-10-09

Unknown User (15:31:52): - Attachment: #3595 MOSES > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ads303/MOSES > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:31:55): Unknown User (15:34:54): - Attachment: #3596 MOSES > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ads303/MOSES > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:34:56): Unknown User (15:41:23): - Attachment: #3597 MOSES > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ads303/MOSES > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:41:26): Unknown User (15:45:31): - Attachment: #3598 MOSES > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/ads303/MOSES > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-10-10

Unknown User (07:13:41): - Attachment: #3599 LimROTS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/AliYoussef96/LimROTS > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:00:01): - Attachment: #3600 Genome wide annotation for Heterorhabditis bacteriophora > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/kabilanbio/Hbacteriophora > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:00:03): Unknown User (09:07:26): - Attachment: #3601 org.Hbacteriophora.eg.db > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/kabilanbio/org.Hbacteriophora.eg.db > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:07:28): Unknown User (09:13:01): - Attachment: #3602 org.Hbacteriophora.eg.db > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/kabilanbio/org.Hbacteriophora.eg.db > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-10-11

Unknown User (03:33:03): - Attachment: #3603 Barbie > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Oshlack/Barbie.git > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (03:33:04): Unknown User (03:34:53): - Attachment: #3604 Barbie > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Oshlack/Barbie > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (03:34:56): Unknown User (09:54:12): Unknown User (09:54:13): Unknown User (09:54:14): Unknown User (09:54:15): Unknown User (15:28:46): - Attachment: #3605 humanHippocampus2024 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/christinehou11/humanHippocampus2024 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:43:49): - Attachment: #3606 probeSNPffer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/gillianmeeks/probeSNPffer > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:43:51):

2024-10-13

Unknown User (19:04:01):

2024-10-14

Unknown User (04:21:38): Unknown User (05:39:55): - Attachment: #3607 SmartPhos > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Lu-Group-UKHD/SmartPhos > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:39:58): Unknown User (05:47:59): - Attachment: #3608 SmartPhos > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Lu-Group-UKHD/SmartPhos > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:48:02): Unknown User (06:15:17): - Attachment: #3609 SmartPhos > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Lu-Group-UKHD/SmartPhos > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:09:59): - Attachment: #3610 probeSNPffer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/gillianmeeks/probeSNPffer > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-10-16

Unknown User (01:30:44): - Attachment: #3611 Barbie > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Oshlack/Barbie > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (01:30:48): Unknown User (01:50:27): - Attachment: #3612 Barbie > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Oshlack/Barbie > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:33:14): - Attachment: #3613 terapadog > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Gionmattia/terapadog.git > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x ] The ‘devel’ branch for new packages and features. > • [ x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:33:15): Unknown User (05:42:48): - Attachment: #3614 terapadog > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Gionmattia/terapadog > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x ] The ‘devel’ branch for new packages and features. > • [ x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:42:49): Unknown User (05:49:07): - Attachment: #3615 terapadog > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/Gionmattia/terapadog > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x ] The ‘devel’ branch for new packages and features. > • [ x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (23:10:42): - Attachment: #3616 plyxp > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/jtlandis/plyxp > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-10-17

Unknown User (19:55:55):

2024-10-21

Unknown User (07:17:30): - Attachment: #3617 poem > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/RoseYuan/poem > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:17:33): Unknown User (07:23:39): - Attachment: #3618 poem > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/RoseYuan/poem > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:03:12): Unknown User (10:03:13): Unknown User (10:03:14): Unknown User (10:03:15): Unknown User (10:03:16): Unknown User (10:03:18): Unknown User (10:03:18): Unknown User (13:40:45): - Attachment: #3619 RUCova > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/molsysbio/RUCova > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:40:47): Unknown User (13:57:06): - Attachment: #3620 RUCova > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/molsysbio/RUCova > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-10-22

Liyang Fei (00:11:24): > @Liyang Fei has joined the channel

Unknown User (07:36:04):

2024-10-24

Unknown User (07:24:37): Unknown User (07:24:38): Unknown User (07:24:39): Unknown User (07:24:41): Unknown User (10:56:18): - Attachment: #3621 XeniumIO > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/waldronlab/XeniumIO/ > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:56:20): Unknown User (11:32:52): - Attachment: #3622 XeniumIO > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/waldronlab/XeniumIO > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-10-25

Unknown User (09:22:34): Unknown User (09:22:35): Unknown User (09:22:36): Unknown User (09:22:37):

2024-10-27

Unknown User (22:22:21): - Attachment: #3623 G4SNVHunter > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/rongxinzh/G4SNVHunter > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-10-28

Unknown User (01:25:24): - Attachment: #3624 TaxSEA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/feargalr/TaxSEA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X ] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (01:25:26): Unknown User (01:26:34): - Attachment: #3625 TaxSEA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/feargalr/TaxSEA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (01:26:36): Unknown User (01:29:31): - Attachment: #3626 TaxSEA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/feargalr/TaxSEA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (01:29:32): Unknown User (01:33:16): - Attachment: #3627 TaxSEA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/feargalr/TaxSEA > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-10-29

Unknown User (00:07:02): - Attachment: #3628 shinyDSP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/kimsjune/shinyDSP > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (00:07:05): Unknown User (00:14:49): - Attachment: #3629 shinyDSP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/kimsjune/shinyDSP > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-10-30

Unknown User (09:30:14): - Attachment: #3630 ELViS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/hyochoi/ELViS > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:30:17): Unknown User (09:56:05): - Attachment: #3631 ELViS > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/hyochoi/ELViS > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-10-31

Unknown User (06:58:38): - Attachment: #3632 JASAPAR2024 sqlite issue > > library(JASPAR2024) > JASPAR2024 <- JASPAR2024() > > > ERROR INFO: > > > adding rname 'https://testjaspar.uio.no/download/database/JASPAR2024.sqlite' > Error in bfcrpath(BiocFileCache(), url) : > not all 'rnames' found or unique. > In addition: Warning messages: > 1: download failed > web resource path: ‘https://testjaspar.uio.no/download/database/JASPAR2024.sqlite’ > local file path: ‘/home/ad/lxhome/l/luoxiao/Linux/.cache/R/BiocFileCache/5584706ccc10_JASPAR2024.sqlite’ > reason: SSL peer certificate or SSH remote key was not OK: [testjaspar.uio.no] SSL certificate problem: certificate has expired > 2: bfcadd() failed; resource removed > rid: BFC15 > fpath: ‘https://testjaspar.uio.no/download/database/JASPAR2024.sqlite’ > reason: download failed > 3: In value[[3L]](cond) : > trying to add rname 'https://testjaspar.uio.no/download/database/JASPAR2024.sqlite' produced error: > bfcadd() failed; see warnings() > >

Unknown User (06:58:40): Unknown User (16:57:21):

2024-11-01

Unknown User (02:07:25): - Attachment: #3633 linkSet > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/GilbertHan1011/linkSet > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (02:07:26): Unknown User (04:00:51): - Attachment: #3634 linkSet > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/GilbertHan1011/linkSet > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:58:06): - Attachment: #3635 miaDash > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/microbiome/miaDash > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:58:07): Unknown User (16:01:17): - Attachment: #3636 miaDash > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository:https://github.com/microbiome/miaDash > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:01:19): Unknown User (16:07:14): - Attachment: #3637 miaDash > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/microbiome/miaDash > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-11-03

Unknown User (15:28:06): - Attachment: #3638 maaslin3 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/biobakery/Maaslin3 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:28:08): Unknown User (15:30:00): - Attachment: #3639 maaslin3 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/biobakery/Maaslin3 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:30:02): Unknown User (15:30:56): - Attachment: #3640 maaslin3 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/biobakery/maaslin3 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:30:58): Unknown User (15:35:24): - Attachment: #3641 maaslin3 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/biobakery/maaslin3 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:35:26): Unknown User (15:39:53): - Attachment: #3642 maaslin3 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/biobakery/maaslin3 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:39:56): Unknown User (15:46:06): - Attachment: #3643 maaslin3 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/biobakery/maaslin3 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-11-04

Unknown User (11:33:24): Unknown User (12:43:09): Unknown User (12:43:10): - Attachment: #3644 Automaic closure of submission issue after submitting package with change of ownership > Hello, > I’d like to resolve an error with github actions on my recent submission. Can you let me know how to proceed? See below, thanks > > > > > Dear @whtns , > > > > > You (or someone) has already posted a repository with the same name to our tracker. > > > > > See https://github.com/Bioconductor/Contributions/issues/3332 > > > > > You cannot post the same repository more than once and packages are not > allowed to have the same name. > > > > > If you would like this repository to be linked to issue number: 3332, > Please contact a Bioconductor Core Member. > I am closing this issue. > > > > > Originally posted by @bioc-issue-bot in https://github.com/Bioconductor/Contributions/issues/3332#issuecomment-2450803097 - Attachment: (inactive) chevreul · Issue #3332 · Bioconductor/Contributions > Update the following URL to point to the GitHub repository of the package you wish to submit to Bioconductor Repository: https://github.com/whtns/chevreul/ Confirm the following by editing each che…

Unknown User (12:45:23): - Attachment: #3645 Automatic closure of submission issue after submitting package with change of ownership > Hello, > I’d like to resolve an error with github actions on my recent submission. Can you let me know how to proceed? See below, thanks > > > > > Dear @whtns , > > > > > You (or someone) has already posted a repository with the same name to our tracker. > > > > > See issue 3332 > > > > > You cannot post the same repository more than once and packages are not > allowed to have the same name. > > > > > If you would like this repository to be linked to issue number: 3332, > Please contact a Bioconductor Core Member. > I am closing this issue.

Unknown User (12:45:26): Unknown User (12:46:01): - Attachment: #3646 Automatic closure of submission issue after submitting package with change of ownership > Hello, > I’d like to resolve an error with github actions on my recent submission. Can you let me know how to proceed? See below, thanks > > > > > Dear @whtns , > > > > > You (or someone) has already posted a repository with the same name to our tracker. > > > > > See issue 3332 > > > > > You cannot post the same repository more than once and packages are not > allowed to have the same name. > > > > > If you would like this repository to be linked to issue number: 3332, > Please contact a Bioconductor Core Member. > I am closing this issue. > > > > > > > > https://github.com/username/reponame

Unknown User (12:46:03): Unknown User (14:42:42): - Attachment: #3647 mist > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/dxd429/mist > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:10:11): - Attachment: #3648 humanHippocampus2024 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/christinehou11/humanHippocampus2024 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:10:14):

2024-11-06

Unknown User (18:45:30): - Attachment: #3649 scHiCcompare > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/dozmorovlab/scHiCcompare > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-11-07

Unknown User (07:57:30): Unknown User (08:13:30): Unknown User (11:58:01):

2024-11-08

Unknown User (00:55:05): - Attachment: #3650 alabaster.sfe > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/pachterlab/alabaster.sfe > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (02:54:59): - Attachment: #3651 beachmat.tiledb > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/tatami-inc/beachmat.tiledb > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:57:02): Unknown User (09:57:21): Unknown User (09:57:55): Unknown User (09:59:17): Unknown User (09:59:37):

2024-11-09

Unknown User (00:23:23): - Attachment: #3652 jazzPanda > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/phipsonlab/jazzPanda > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (00:23:26):

2024-11-10

Unknown User (20:06:52): - Attachment: #3653 biocmake > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/LTLA/biocmake > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-11-11

Unknown User (07:15:57):

2024-11-13

Unknown User (00:49:06): - Attachment: #3654 LongMod123 > I wish to submit this package as a workflow. > > > > > • Repository: https://github.com/mritchielab/LongMod123 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (00:49:08): Unknown User (01:00:32): - Attachment: #3655 LongMod123 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > > > > • Repository: https://github.com/mritchielab/LongMod123 > > > > > Confirm the following by editing each check box to ‘[x]’ > > > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > > > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > > > > [1]: https://contributions.bioconductor.org/ > > [2]: https://bioconductor.org/developers/package-submission/ > > [3]: https://support.bioconductor.org > > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > > [5]: http://bioconductor.org/developers/how-to/git/ > > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > > [7]: https://bioconductor.org/about/code-of-conduct/ > > [8]: https://bioconductor.org/ > > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (01:00:35):

2024-11-14

Unknown User (10:28:11):

2024-11-15

Unknown User (07:18:12):

2024-11-18

Unknown User (07:15:54): Unknown User (07:15:55): Unknown User (07:18:53): Unknown User (16:05:28): - Attachment: #3656 OmicGsea package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/xuz1/OmicGsea > > Confirm the following by editing each check box to ‘[x]’ > > • [X ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X ] The ‘devel’ branch for new packages and features. > • [X ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X ] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:05:30):

2024-11-19

Unknown User (05:56:41): - Attachment: #3657 TCMC > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/danymukesha/TCMC > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-11-21

Unknown User (00:00:11): - Attachment: #3658 CPSM: Cancer patient survival model > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hks5august/CPSM > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (00:00:14): Unknown User (07:36:42): Unknown User (09:36:52): - Attachment: #3659 OmicGsea R package submission > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/xuz1/OmicGsea > > Confirm the following by editing each check box to ‘[x]’ > > • [X ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X ] The ‘devel’ branch for new packages and features. > • [X ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X ] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-11-22

Unknown User (07:18:33): Unknown User (07:18:34): Unknown User (09:56:44): - Attachment: #3660 anglemania > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/BIMSBbioinfo/anglemania > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:56:46):

2024-11-25

Unknown User (00:12:13):

2024-11-26

Unknown User (07:28:15): Unknown User (11:13:59): - Attachment: #3661 anglemania > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/BIMSBbioinfo/anglemania/ > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-11-27

Unknown User (12:18:07): - Attachment: #3662 OmicGsea > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/xuz1/OmicGsea > > Confirm the following by editing each check box to ‘[x]’ > > • [X ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X ] The ‘devel’ branch for new packages and features. > • [X ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X ] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:18:10):

2024-11-28

Unknown User (09:01:21): - Attachment: #3663 Site2Target > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:01:23): Unknown User (09:07:22): - Attachment: #3664 Site2Target package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/fls-bioinformatics-core/Site2Target > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:07:24): Unknown User (09:11:25): - Attachment: #3665 Site2Target > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/fls-bioinformatics-core/Site2Target > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:11:27): Unknown User (09:21:34): - Attachment: #3666 Site2Target > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/fls-bioinformatics-core/Site2Target > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-11-29

Unknown User (05:40:30): - Attachment: #3667 https://github.com/ASPresearch/Lheuristic > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [X ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:40:32): Unknown User (05:46:50): - Attachment: #3668 Lheuristic. Detection of scatterplots with L-shaped pattern for the study of gene expression regulation by methylation > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ASPresearch/Lheuristic > > Confirm the following by editing each check box to ‘[x]’ > > • [X ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:46:54): Unknown User (08:16:05):

2024-12-01

Unknown User (12:35:36): - Attachment: #3669 Lheuristic. Detection of scatterplots with L-shaped pattern for the study of gene expression regulation by methylation > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ASPresearch/Lheuristic > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:35:39): Unknown User (13:25:37): - Attachment: #3670 RbowtieCuda > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/FranckRICHARD01/RbowtieCuda > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:25:38): Unknown User (13:37:15): - Attachment: #3671 RbowtieCuda > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/FranckRICHARD01/RbowtieCuda > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:37:17): Unknown User (14:27:45): - Attachment: #3672 RbowtieCuda > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/FranckRICHARD01/RbowtieCuda > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:32:08): - Attachment: #3673 h5mread > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hpages/h5mread > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-12-02

Unknown User (17:11:58): - Attachment: #3674 QRscore > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/songlab-cal/QRscore/ > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:12:00): Unknown User (22:16:21): - Attachment: #3675 QRscore > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/songlab-cal/QRscore > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-12-03

Unknown User (09:42:34):

2024-12-04

Unknown User (14:32:02): Unknown User (19:44:20): - Attachment: #3676 PICB > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/HaaseLab/PICB > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about the output of the automatic reports generated by the SPB (Single Package Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-12-06

Unknown User (08:04:06): Unknown User (08:08:47):

2024-12-09

Unknown User (13:18:59): - Attachment: #3677 CCAFE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/wolffha/CCAFE > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-12-10

Unknown User (07:58:50): Unknown User (07:59:12): Unknown User (08:00:11): Unknown User (13:24:49):

2024-12-12

Unknown User (00:56:56): - Attachment: #3678 SVP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/YuLab-SMU/SVP > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (00:56:59): Unknown User (04:05:44): - Attachment: #3679 SVP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/YuLab-SMU/SVP > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (23:50:34): - Attachment: #3680 dandelionR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/tuonglab/dandelionR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-12-15

Unknown User (13:22:46): - Attachment: #3681 TrIdent > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jlmaier12/TrIdent > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-12-16

Unknown User (08:53:49): - Attachment: #3682 muSpaData > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/peicai/muSpaData > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:35:32):

2024-12-19

Unknown User (08:39:30): - Attachment: #3683 BCalm > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/kircherlab/BCalm > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:39:32): Unknown User (09:29:44): - Attachment: #3684 BCalm > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/kircherlab/BCalm > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-12-22

Unknown User (20:51:14): - Attachment: #3685 RamEx > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/qibebt-bioinfo/RamEx > > Confirm the following by editing each check box to ‘[x]’ > > • [√] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [√] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [√] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [√] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [√] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [√] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [√] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [√] The ‘devel’ branch for new packages and features. > • [√] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [√] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:51:16):

2024-12-24

Unknown User (14:12:14): - Attachment: #3686 org.Hbacteriophora.eg.db > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:12:15): Unknown User (14:14:00): - Attachment: #3687 org.Hbacteriophora.eg.db > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/kabilanbio/org.Hbacteriophora.eg.db > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:14:03): Unknown User (14:20:24): - Attachment: #3688 org.Hbacteriophora.eg.db > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/kabilanbio/org.Hbacteriophora.eg.db > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:20:26): Unknown User (14:21:07): - Attachment: #3689 Dear @kabilanbio , > > Dear @kabilanbio , > > > You (or someone) has already posted that repository to our tracker. > > See https://github.com/Bioconductor/Contributions/issues/3602 > > You cannot post the same repository more than once. > > If you would like this repository to be linked to issue number: 3688, > Please contact a Bioconductor Core Member. > I am closing this issue. > > Originally posted by @bioc-issue-bot in https://github.com/Bioconductor/Contributions/issues/3688#issuecomment-2561360222 - Attachment: (inactive) org.Hbacteriophora.eg.db · Issue #3688 · Bioconductor/Contributions > Update the following URL to point to the GitHub repository of the package you wish to submit to Bioconductor Repository: https://github.com/kabilanbio/org.Hbacteriophora.eg.db Confirm the following…

Unknown User (14:21:07): Unknown User (14:22:00): - Attachment: #3690 Dear @kabilanbio , > > Dear @kabilanbio , > > > I found more than one GitHub URL in your issue. Please make sure there > is only one, it should look like: > > https://github.com/username/reponame > > I am closing this issue. Please try again with a new issue. > > Originally posted by @bioc-issue-bot in https://github.com/Bioconductor/Contributions/issues/3689#issuecomment-2561360458

Unknown User (14:22:01):

2024-12-29

Unknown User (08:51:03): - Attachment: #3691 PlasmodiumgenomeData Submission for ExperimentHub > The PlasmodiumgenomeData package provides curated genome datasets for various Plasmodium species, supporting bioinformatics and genomic analyses. This package includes preprocessed genomic data in .rds format, which is ideal for integration with R-based workflows. The data is intended for researchers studying Plasmodium genetics and related fields. > > GitHub Repository > The package source code is hosted on GitHub: > [PlasmodiumgenomeData Repository](https://github.com/ocheab/PlasmodiumgenomeData) > > Adherence to Bioconductor Guidelines > • The package adheres to Bioconductor’s guidelines. > • It includes a valid metadata.csv file located in inst/extdata/. > • The data files are appropriately managed using Git LFS for large file handling. > > Request > We kindly request the inclusion of PlasmodiumgenomeData in ExperimentHub. Please let us know if there are any additional requirements or modifications needed for submission. > > Thank you for your time and consideration. > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2024-12-30

Unknown User (00:52:12): - Attachment: #3692 MultimodalGraphics: an R package for graphical integration of multimodal datasets > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/famanalytics0/MultiModalGraphics > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (00:52:14): Unknown User (00:55:22): - Attachment: #3693 MultimodalGraphics: an R package for visual integration of multimodal datasets > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yourusername/yourpackagename > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (00:55:24): Unknown User (01:04:46): - Attachment: #3694 MultimodalGraphics: an R package for graphical integration of multimodal datasets > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/famanalytics0/MultiModalGraphics > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ ] The ‘devel’ branch for new packages and features. > • [ ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ ] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (01:04:49): Unknown User (10:04:51): Unknown User (10:10:55): Unknown User (10:56:39): - Attachment: #3695 org.Hbacteriophora.eg.db > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/kabilanbio/org.Hbacteriophora.eg.db > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:56:42):

2025-01-02

Unknown User (05:41:31): - Attachment: #3696 New Package Submission: BreastSubtypeR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/yqkiuo/BreastSubtypeR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (07:20:54): Unknown User (07:34:13): Unknown User (17:32:55): Unknown User (18:39:33): - Attachment: #3697 limpa > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • https://github.com/SmythLab/limpa > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (18:39:36): Unknown User (19:03:17): - Attachment: #3698 limpa > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/SmythLab/limpa > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2025-01-03

Unknown User (22:24:15): - Attachment: #3699 crumblr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/DiseaseNeurogenomics/crumblr > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2025-01-05

Unknown User (21:35:57): - Attachment: #3700 RamEx > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/qibebt-bioinfo/RamEx > > Confirm the following by editing each check box to ‘[x]’ > > • [√ ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [√] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [√] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [√] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [√] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [√] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [√] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [√] The ‘devel’ branch for new packages and features. > • [√] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [√] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2025-01-07

Unknown User (11:05:36): Unknown User (11:05:43): Unknown User (22:23:28): - Attachment: #3701 Bulk RNA-seq Gene Mapping and Analysis Tutorial > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/mdbabumiamssm/GENE-MAPPING > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:23:30): Unknown User (23:10:03): - Attachment: #3702 Bulk RNA-seq Analysis with Gene Mapping from Ensembl to R Studio > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/mdbabumiamssm/GENE-MAPPING > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2025-01-09

Unknown User (10:38:50): Unknown User (10:56:12):

2025-01-10

Unknown User (16:26:15): - Attachment: #3703 islify > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jtheorell/islify > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:26:18):

2025-01-12

Unknown User (15:09:25): - Attachment: #3704 islify > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jtheorell/islify > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2025-01-13

Unknown User (07:22:40): Unknown User (10:08:36): Unknown User (12:55:26): Unknown User (12:55:27): Unknown User (12:55:28): Unknown User (12:55:30):

2025-01-14

Unknown User (14:08:30): Unknown User (14:10:24): Unknown User (14:15:33): Unknown User (14:57:07): - Attachment: #3705 scLANE > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jr-leary7/scLANE > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2025-01-16

Unknown User (10:43:17):

2025-01-17

Unknown User (15:16:03): - Attachment: #3706 placentaImmuneCellRefEPIC450k > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/kyleac/placentaImmuneCellRefEPIC450k > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:16:05): Unknown User (15:19:00): - Attachment: #3707 placentaImmuneCellRefEPIC450k > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/kyleac/placentaImmuneCellRefEPIC450k > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:19:01): Unknown User (15:19:52): - Attachment: #3708 placentaImmuneCellRefEPIC450k > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/kyleac/placentaImmuneCellRefEPIC450k > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (15:19:54): Unknown User (15:27:48): - Attachment: #3709 placentaImmuneCellRefEPIC450k > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/kyleac/placentaImmuneCellRefEPIC450k > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (19:11:49): Unknown User (19:11:50): Unknown User (19:11:51): Unknown User (19:11:52): Unknown User (19:11:53):

2025-01-18

Unknown User (20:44:58): - Attachment: #3710 dmGsea > The R package dmGsea provides gene set enrichment analysis functions for complex Omics data. In many omics datasets, such as Illumina DNA methylation data, genes are often represented by variable numbers of correlated probes, and a single probe may map to multiple genes. This complex data structure poses significant challenges for gene set enrichment analysis. The dmGsea package addresses these challenges by providing both threshold- and ranking-based competitive enrichment analysis methods, effectively accounting for probe correlation and probe number bias. These versatile functions can be applied to a wide range of omics datasets, including DNA methylation, proteomics and gene expression data.

Unknown User (20:45:00): Unknown User (20:47:43): - Attachment: #3711 dmGsea > The R package dmGsea provides gene set enrichment analysis functions for complex Omics data. In many omics datasets, such as Illumina DNA methylation data, genes are often represented by variable numbers of correlated probes, and a single probe may map to multiple genes. This complex data structure poses significant challenges for gene set enrichment analysis. The dmGsea package addresses these challenges by providing both threshold- and ranking-based competitive enrichment analysis methods, effectively accounting for probe correlation and probe number bias. These versatile functions can be applied to a wide range of omics datasets, including DNA methylation, proteomics and gene expression data. The github repository is https://github.com/xuz1/dmGsea

Unknown User (20:59:55):

2025-01-21

Unknown User (23:10:21): - Attachment: #3712 HVP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > Repository: https://github.com/dblux/HVP > Confirm the following by editing each check box to ‘[x]’ > > > [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > > [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > > [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > > [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > > [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > > [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > > [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > > [x] The ‘devel’ branch for new packages and features. > > [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > > [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up.

2025-01-23

Unknown User (13:26:40): - Attachment: #3713 DNAcycP2 > https://github.com/jipingw/DNAcycP2

Unknown User (13:26:41): Unknown User (13:32:13): - Attachment: #3714 DNAcycP2 > https://github.com/jipingw/DNAcycP2

Unknown User (13:32:16):

2025-01-24

Unknown User (07:00:35): - Attachment: #3715 DNAcycP2 > https://github.com/jipingw/DNAcycP2

2025-01-28

Unknown User (08:03:36): Unknown User (08:13:21): Unknown User (08:16:00):

2025-01-29

Unknown User (12:11:58): Unknown User (12:11:59): Unknown User (12:12:01):

2025-01-30

Unknown User (18:46:46): - Attachment: #3716 LongMod123 > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/mritchielab/LongMod123 > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:37:24): - Attachment: #3717 stPipe > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/mritchielab/stPipe > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:39:29): Unknown User (22:42:48): - Attachment: #3718 stPipe > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/mritchielab/stPipe > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:42:50): Unknown User (22:49:05): - Attachment: #3719 stPipe > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/mritchielab/stPipe > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (22:49:08): Unknown User (22:52:49): - Attachment: #3720 stPipe > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/mritchielab/stPipe > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2025-02-03

Unknown User (13:11:19): Unknown User (13:11:20): Unknown User (13:11:21): Unknown User (13:19:14): Unknown User (13:40:59):

2025-02-05

Unknown User (04:54:29): Unknown User (04:54:29): - Attachment: #3721 Error in .calculatePeakGeneCorrelations(GRN, TADs = TADs, knownLinks = knownLinks, : all(!is.na(map_peaks)) is not TRUE. In normarg_seqnames2(seqnames, seqinfo) : levels in ‘seqnames’ with no entries in ‘seqinfo’ were dropped > Hello. > > I am in the middle of https://grp-zaugg.embl-community.io/GRaNIE/articles/GRaNIE_workflow.html tutorial and got this error: > > > GRN = addConnections_peak_gene( > • GRN, # El objeto GRN que contiene la información de los datos de RNA-seq y ATAC-seq > • overlapTypeGene = “TSS”, # Usar TSS como referencia para la búsqueda de genes cercanos a los picos > • corMethod = “pearson”, # Usar el coeficiente de correlación de Pearson > • promoterRange = 50000, # El rango de la vecindad en bp para correlacionar picos y genes > • TADs = NULL, # No se proporcionan TADs > • TADs_mergeOverlapping = FALSE, # No se usa este parámetro ya que no tienes TADs > • knownLinks = NULL, # No se utilizan enlaces conocidos > • knownLinks_separator = c(“:”, “-”), # Separadores para los enlaces conocidos (no utilizados) > • knownLinks_useExclusively = FALSE, # No se usan exclusivamente los enlaces conocidos > • shuffleRNACounts = TRUE, # Aleatorizar las etiquetas de RNA > • nCores = 2, # Usar 4 núcleos para el análisis > • plotDiagnosticPlots = TRUE, # Generar gráficos de diagnóstico > • plotGeneTypes = list(c(“all”), c(“protein_coding”)), # Mostrar todos los tipos de genes y solo los codificantes > • outputFolder = NULL, # Usar el directorio de salida predeterminado > • forceRerun = TRUE # No forzar la ejecución si los resultados ya existen > • ) > INFO [2025-02-05 03:11:45] > Preparing data > > INFO [2025-02-05 03:11:45] Calculate peak gene overlaps based on either a fixed neighborhood size or defined TADs… > INFO [2025-02-05 03:11:45] Extend peaks based on user-defined extension size of 50000 up- and downstream. > INFO [2025-02-05 03:11:45] Finished successfully. Execution time: 0.2 secs > INFO [2025-02-05 03:11:45] Source distribution of peak-gene links: > INFO [2025-02-05 03:11:45] neighborhood: 73672 > INFO [2025-02-05 03:11:45] > Finished preparing data > > INFO [2025-02-05 03:11:45] > Calculate peak-gene correlations for real data > > Error en .calculatePeakGeneCorrelations(GRN, TADs = TADs, knownLinks = knownLinks, : > all(!is.na(map_peaks)) is not TRUE > Además: Aviso: > In normarg_seqnames2(seqnames, seqinfo) : > levels in ‘seqnames’ with no entries in ‘seqinfo’ were dropped > > GRN = addConnections_peak_gene(GRN, corMethod = “spearman”, promoterRange = 10000, > • > TADs = NULL, nCores = 1, plotDiagnosticPlots = T, plotGeneTypes = list(c("all")), > > • > forceRerun = TRUE) > > INFO [2025-02-05 03:12:57] > Preparing data > > INFO [2025-02-05 03:12:57] Calculate peak gene overlaps based on either a fixed neighborhood size or defined TADs… > INFO [2025-02-05 03:12:57] Extend peaks based on user-defined extension size of 10000 up- and downstream. > INFO [2025-02-05 03:12:58] Finished successfully. Execution time: 0.3 secs > INFO [2025-02-05 03:12:58] Source distribution of peak-gene links: > INFO [2025-02-05 03:12:58] neighborhood: 21510 > INFO [2025-02-05 03:12:58] > Finished preparing data > > INFO [2025-02-05 03:12:58] > Calculate peak-gene correlations for real data > > Error en .calculatePeakGeneCorrelations(GRN, TADs = TADs, knownLinks = knownLinks, : > all(!is.na(map_peaks)) is not TRUE > Además: Aviso: > In normarg_seqnames2(seqnames, seqinfo) : > levels in ‘seqnames’ with no entries in ‘seqinfo’ were dropped > > These are my inputs: > > head(dna) > > peakID M1 M2 M3 M4 M5 M6 > > 1 chr1:10000-10460 406 746 714 879 404 603 > > 2 chr1:19100-19140 3 10 4 3 2 8 > > 3 chr1:29040-29400 73 66 104 81 75 77 > > 4 chr1:131880-131940 7 4 6 5 1 6 > > 5 chr1:180740-181000 151 275 467 451 293 293 > > 6 chr1:181640-181860 33 53 76 63 50 31 > > head(rna_data) > > ensemblID M1 M2 M3 M4 M5 M6 > > 1 ENSG00000227232 95 83 145 209 186 275 > > 2 ENSG00000278267 18 3 13 22 18 43 > > 3 ENSG00000268903 40 14 3 8 26 17 > > 4 ENSG00000269981 27 19 0 10 24 21 > > 5 ENSG00000241860 19 8 7 12 10 6 > > 6 ENSG00000279457 246 135 325 449 114 188 > > someone please could help me?

Unknown User (04:55:58): - Attachment: #3722 all(!is.na(map_peaks)) is not TRUE. In normarg_seqnames2(seqnames, seqinfo) : levels in ‘seqnames’ with no entries in ‘seqinfo’ were dropped > Hello. > > I am in the middle of https://grp-zaugg.embl-community.io/GRaNIE/articles/GRaNIE_workflow.html tutorial and got this error: > > > GRN = addConnections_peak_gene( > • GRN, # El objeto GRN que contiene la información de los datos de RNA-seq y ATAC-seq > • overlapTypeGene = “TSS”, # Usar TSS como referencia para la búsqueda de genes cercanos a los picos > • corMethod = “pearson”, # Usar el coeficiente de correlación de Pearson > • promoterRange = 50000, # El rango de la vecindad en bp para correlacionar picos y genes > • TADs = NULL, # No se proporcionan TADs > • TADs_mergeOverlapping = FALSE, # No se usa este parámetro ya que no tienes TADs > • knownLinks = NULL, # No se utilizan enlaces conocidos > • knownLinks_separator = c(“:”, “-”), # Separadores para los enlaces conocidos (no utilizados) > • knownLinks_useExclusively = FALSE, # No se usan exclusivamente los enlaces conocidos > • shuffleRNACounts = TRUE, # Aleatorizar las etiquetas de RNA > • nCores = 2, # Usar 4 núcleos para el análisis > • plotDiagnosticPlots = TRUE, # Generar gráficos de diagnóstico > • plotGeneTypes = list(c(“all”), c(“protein_coding”)), # Mostrar todos los tipos de genes y solo los codificantes > • outputFolder = NULL, # Usar el directorio de salida predeterminado > • forceRerun = TRUE # No forzar la ejecución si los resultados ya existen > • ) > INFO [2025-02-05 03:11:45] > Preparing data > > INFO [2025-02-05 03:11:45] Calculate peak gene overlaps based on either a fixed neighborhood size or defined TADs… > INFO [2025-02-05 03:11:45] Extend peaks based on user-defined extension size of 50000 up- and downstream. > INFO [2025-02-05 03:11:45] Finished successfully. Execution time: 0.2 secs > INFO [2025-02-05 03:11:45] Source distribution of peak-gene links: > INFO [2025-02-05 03:11:45] neighborhood: 73672 > INFO [2025-02-05 03:11:45] > Finished preparing data > > INFO [2025-02-05 03:11:45] > Calculate peak-gene correlations for real data > > Error en .calculatePeakGeneCorrelations(GRN, TADs = TADs, knownLinks = knownLinks, : > all(!is.na(map_peaks)) is not TRUE > Además: Aviso: > In normarg_seqnames2(seqnames, seqinfo) : > levels in ‘seqnames’ with no entries in ‘seqinfo’ were dropped > > GRN = addConnections_peak_gene(GRN, corMethod = “spearman”, promoterRange = 10000, > • > TADs = NULL, nCores = 1, plotDiagnosticPlots = T, plotGeneTypes = list(c("all")), > > • > forceRerun = TRUE) > > INFO [2025-02-05 03:12:57] > Preparing data > > INFO [2025-02-05 03:12:57] Calculate peak gene overlaps based on either a fixed neighborhood size or defined TADs… > INFO [2025-02-05 03:12:57] Extend peaks based on user-defined extension size of 10000 up- and downstream. > INFO [2025-02-05 03:12:58] Finished successfully. Execution time: 0.3 secs > INFO [2025-02-05 03:12:58] Source distribution of peak-gene links: > INFO [2025-02-05 03:12:58] neighborhood: 21510 > INFO [2025-02-05 03:12:58] > Finished preparing data > > INFO [2025-02-05 03:12:58] > Calculate peak-gene correlations for real data > > Error en .calculatePeakGeneCorrelations(GRN, TADs = TADs, knownLinks = knownLinks, : > all(!is.na(map_peaks)) is not TRUE > Además: Aviso: > In normarg_seqnames2(seqnames, seqinfo) : > levels in ‘seqnames’ with no entries in ‘seqinfo’ were dropped > > These are my inputs: > > head(dna) > > peakID M1 M2 M3 M4 M5 M6 > > 1 chr1:10000-10460 406 746 714 879 404 603 > > 2 chr1:19100-19140 3 10 4 3 2 8 > > 3 chr1:29040-29400 73 66 104 81 75 77 > > 4 chr1:131880-131940 7 4 6 5 1 6 > > 5 chr1:180740-181000 151 275 467 451 293 293 > > 6 chr1:181640-181860 33 53 76 63 50 31 > > head(rna_data) > > ensemblID M1 M2 M3 M4 M5 M6 > > 1 ENSG00000227232 95 83 145 209 186 275 > > 2 ENSG00000278267 18 3 13 22 18 43 > > 3 ENSG00000268903 40 14 3 8 26 17 > > 4 ENSG00000269981 27 19 0 10 24 21 > > 5 ENSG00000241860 19 8 7 12 10 6 > > 6 ENSG00000279457 246 135 325 449 114 188 > > someone please could help me?

Unknown User (04:55:59): Unknown User (04:56:25): - Attachment: #3723 all(!is.na(map_peaks)) is not TRUE. In normarg_seqnames2(seqnames, seqinfo) : levels in ‘seqnames’ with no entries in ‘seqinfo’ were dropped > Hello. > > I am in the middle of GRaNIE_workflow tutorial and got this error: > > > GRN = addConnections_peak_gene( > • GRN, # El objeto GRN que contiene la información de los datos de RNA-seq y ATAC-seq > • overlapTypeGene = “TSS”, # Usar TSS como referencia para la búsqueda de genes cercanos a los picos > • corMethod = “pearson”, # Usar el coeficiente de correlación de Pearson > • promoterRange = 50000, # El rango de la vecindad en bp para correlacionar picos y genes > • TADs = NULL, # No se proporcionan TADs > • TADs_mergeOverlapping = FALSE, # No se usa este parámetro ya que no tienes TADs > • knownLinks = NULL, # No se utilizan enlaces conocidos > • knownLinks_separator = c(“:”, “-”), # Separadores para los enlaces conocidos (no utilizados) > • knownLinks_useExclusively = FALSE, # No se usan exclusivamente los enlaces conocidos > • shuffleRNACounts = TRUE, # Aleatorizar las etiquetas de RNA > • nCores = 2, # Usar 4 núcleos para el análisis > • plotDiagnosticPlots = TRUE, # Generar gráficos de diagnóstico > • plotGeneTypes = list(c(“all”), c(“protein_coding”)), # Mostrar todos los tipos de genes y solo los codificantes > • outputFolder = NULL, # Usar el directorio de salida predeterminado > • forceRerun = TRUE # No forzar la ejecución si los resultados ya existen > • ) > INFO [2025-02-05 03:11:45] > Preparing data > > INFO [2025-02-05 03:11:45] Calculate peak gene overlaps based on either a fixed neighborhood size or defined TADs… > INFO [2025-02-05 03:11:45] Extend peaks based on user-defined extension size of 50000 up- and downstream. > INFO [2025-02-05 03:11:45] Finished successfully. Execution time: 0.2 secs > INFO [2025-02-05 03:11:45] Source distribution of peak-gene links: > INFO [2025-02-05 03:11:45] neighborhood: 73672 > INFO [2025-02-05 03:11:45] > Finished preparing data > > INFO [2025-02-05 03:11:45] > Calculate peak-gene correlations for real data > > Error en .calculatePeakGeneCorrelations(GRN, TADs = TADs, knownLinks = knownLinks, : > all(!is.na(map_peaks)) is not TRUE > Además: Aviso: > In normarg_seqnames2(seqnames, seqinfo) : > levels in ‘seqnames’ with no entries in ‘seqinfo’ were dropped > > GRN = addConnections_peak_gene(GRN, corMethod = “spearman”, promoterRange = 10000, > • > TADs = NULL, nCores = 1, plotDiagnosticPlots = T, plotGeneTypes = list(c("all")), > > • > forceRerun = TRUE) > > INFO [2025-02-05 03:12:57] > Preparing data > > INFO [2025-02-05 03:12:57] Calculate peak gene overlaps based on either a fixed neighborhood size or defined TADs… > INFO [2025-02-05 03:12:57] Extend peaks based on user-defined extension size of 10000 up- and downstream. > INFO [2025-02-05 03:12:58] Finished successfully. Execution time: 0.3 secs > INFO [2025-02-05 03:12:58] Source distribution of peak-gene links: > INFO [2025-02-05 03:12:58] neighborhood: 21510 > INFO [2025-02-05 03:12:58] > Finished preparing data > > INFO [2025-02-05 03:12:58] > Calculate peak-gene correlations for real data > > Error en .calculatePeakGeneCorrelations(GRN, TADs = TADs, knownLinks = knownLinks, : > all(!is.na(map_peaks)) is not TRUE > Además: Aviso: > In normarg_seqnames2(seqnames, seqinfo) : > levels in ‘seqnames’ with no entries in ‘seqinfo’ were dropped > > These are my inputs: > > head(dna) > > peakID M1 M2 M3 M4 M5 M6 > > 1 chr1:10000-10460 406 746 714 879 404 603 > > 2 chr1:19100-19140 3 10 4 3 2 8 > > 3 chr1:29040-29400 73 66 104 81 75 77 > > 4 chr1:131880-131940 7 4 6 5 1 6 > > 5 chr1:180740-181000 151 275 467 451 293 293 > > 6 chr1:181640-181860 33 53 76 63 50 31 > > head(rna_data) > > ensemblID M1 M2 M3 M4 M5 M6 > > 1 ENSG00000227232 95 83 145 209 186 275 > > 2 ENSG00000278267 18 3 13 22 18 43 > > 3 ENSG00000268903 40 14 3 8 26 17 > > 4 ENSG00000269981 27 19 0 10 24 21 > > 5 ENSG00000241860 19 8 7 12 10 6 > > 6 ENSG00000279457 246 135 325 449 114 188 > > someone please could help me?

Unknown User (04:56:27):

2025-02-06

Unknown User (21:26:58): - Attachment: #3724 Rlibigraph > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/libscran/Rlibigraph > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (21:27:01): Unknown User (21:29:00): - Attachment: #3725 Rlibigraph > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/libscran/Rlibigraph > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2025-02-07

Unknown User (11:18:38): - Attachment: #3726 SVP > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/YuLab-SMU/SVP > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:18:40): Unknown User (11:20:13):

2025-02-10

Unknown User (13:47:17):

2025-02-12

Unknown User (11:51:05): - Attachment: #3727 TRADE > I would like to submit this package, titled TRADE, to bioconductor: > > https://github.com/ajaynadig/TRADE > > I confirm that I understand the review process, package guidelines, and maintainer responsibilities. > > Thank you!

Unknown User (11:51:07):

2025-02-14

Unknown User (11:25:31): - Attachment: #3728 Coralysis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/elolab/Coralysis > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:25:33): Unknown User (12:21:55): - Attachment: #3729 Coralysis > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/elolab/Coralysis > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2025-02-16

Unknown User (14:24:08): - Attachment: #3730 decemedip > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/nshen7/decemedip > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (19:11:43):

2025-02-17

Unknown User (10:34:08): - Attachment: #3731 OSTA.data > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/estellad/OSTA.data > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:57:43): - Attachment: #3732 pathMED > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jordimartorell/pathMED > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:58:53): - Attachment: #3733 peakCombiner > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Novartis/peakCombiner > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:58:56):

2025-02-18

Unknown User (03:22:09): - Attachment: #3734 SigFun > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > Repository: https://github.com/BioinfOMICS/SigFun > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (09:44:14): - Attachment: #3735 methylTracer > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/zetian-jia/methylTracer > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:57:37): - Attachment: #3736 TRADEtools > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ajaynadig/TRADEtools > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ]x I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ]x I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:57:39): Unknown User (12:59:55): - Attachment: #3737 TRADEtools > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ajaynadig/TRADEtools > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ]x I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ]x I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:59:58): Unknown User (13:36:00): - Attachment: #3738 TRADEtools > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ajaynadig/TRADEtools > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ ]x I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ ]x I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:48:02): Unknown User (13:48:03): Unknown User (13:48:05): Unknown User (13:48:06): Unknown User (13:48:07): Unknown User (13:48:08): Unknown User (13:48:10):

2025-02-19

Unknown User (12:05:22): - Attachment: #3739 spacexr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ggrajeda/spacexr > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:05:26): Unknown User (12:26:04): - Attachment: #3740 spacexr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ggrajeda/spacexr > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (12:26:07): Unknown User (12:28:57): - Attachment: #3741 spacexr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ggrajeda/spacexr > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2025-02-20

Unknown User (11:14:48): Unknown User (14:04:24): - Attachment: #3742 add Clonality package back to Bioconductor > Hi, > the package was removed because I didn’t fix some errors that appeared in time (I fixed them in Github repository but it failed to push up). Can you please add Clonality package back to Bioconductor? > https://github.com/IOstrovnaya/Clonality > > Thanks! > Irina

Unknown User (14:04:26): Unknown User (14:07:24): - Attachment: #3743 clonality package > Hi, > the package was removed because I didn’t fix some errors that appeared in time (I fixed them in Github repository but it failed to push up). Can you please add Clonality package back to Bioconductor? > https://github.com/IOstrovnaya/Clonality > > Thanks! > Irina

Unknown User (14:07:26): Unknown User (14:11:02): - Attachment: #3744 clonality package > Hi, > the package was removed because I didn’t fix some errors that appeared in time (I fixed them in Github repository but it failed to push up). Can you please add Clonality package back to Bioconductor? > https://github.com/IOstrovnaya/Clonality > > Thanks! > Irina

Unknown User (14:11:06): Unknown User (14:17:01): - Attachment: #3745 clonality package > Hi, > the package was removed because I didn’t fix some errors that appeared in time (I fixed them in Github repository but it failed to push up). Can you please add Clonality package back to Bioconductor? > https://github.com/IOstrovnaya/Clonality > > Thanks! > Irina

Unknown User (14:17:04): Unknown User (22:55:24): - Attachment: #3746 barbieQ

Unknown User (22:55:29): Unknown User (23:27:51): - Attachment: #3747 barbieQ > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Oshlack/barbieQ > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2025-02-25

Unknown User (04:01:59): - Attachment: #3748 LipidTrend > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/BioinfOMICS/LipidTrend > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:55:14): - Attachment: #3749 Ibex > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/BorchLab/Ibex > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:47:18): - Attachment: #3750 DropSift > https://github.com/broadinstitute/DropSift

2025-02-26

Unknown User (09:30:44):

2025-02-27

Unknown User (08:49:52): - Attachment: #3751 notame > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/hanhineva-lab/notame > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2025-02-28

Unknown User (15:38:56): - Attachment: #3752 PathwayVolcano tool > [Submission] PathwayVolcano > > Package Information > • Package Name: PathwayVolcano > • Short Description: An R package for visualizing pathway enrichment results using volcano plots. > • GitHub Repository: https://github.com/thoconne/PathwayVolcano > • Bioconductor Maintainer: Thomas O'Connell <thoconne@iu.edu> > > Summary of the Package > PathwayVolcano is an R package that provides interactive volcano plots for pathway enrichment analysis. It allows researchers to: > • Visualize pathway significance vs. fold-change data. > • Highlight significant pathways dynamically. > • Customize plots for publication-ready figures. > > The package is designed to work with Bioconductor enrichment analysis tools, such as clusterProfiler and ReactomePA. > > R CMD Build and Check > Results from R CMD Check (on R-devel): > • :white_check_mark: No ERRORS > • :white_check_mark: No WARNINGS > • :white_check_mark: No NOTES > > > * checking package dependencies ... OK > * checking installed package size ... NOTE > installed size is 5.1Mb > * checking R code for possible problems ... OK > > > Bioconductor Compliance > • :white_check_mark: BiocCheck::BiocCheckGitClone("PathwayVolcano") passes without errors. > • :white_check_mark: Package follows Bioconductor coding standards. > • :white_check_mark: Includes a vignette and unit tests. > > Additional Comments > • This package was inspired by pathway visualization limitations in existing Bioconductor tools. > • The package provides high-resolution plots with ggplot2 and plotly interactivity. > • I am open to feedback and improvements based on the Bioconductor review. > > Maintainer Confirmation > I confirm that: > • [x] I have read the Bioconductor Package Submission Guidelines. > • [x] My package follows Bioconductor best practices. > • [x] I am prepared to actively maintain this package. > > Next Steps > Once submitted, a Bioconductor reviewer will: > 1. Verify package structure & dependencies. > 2. Run additional compliance checks. > 3. Provide review comments (typically within 2-6 weeks). > 4. Approve package after revisions.

Unknown User (17:17:14): - Attachment: #3753 BatchSVG > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/christinehou11/BatchSVG > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2025-03-02

Unknown User (20:21:20): - Attachment: #3754 ploidyPeaks > My previous ticket had been closed due to inactivity. I’ve had a surplus of time to make necessary changes in order to get my package ready for submission. Hoping to re-open the ticket here.

Unknown User (20:21:22): Unknown User (20:23:03): - Attachment: #3755 ploidyPeaks > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/MicroStatsLab/PloidyPeaks > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:23:06):

2025-03-03

Unknown User (07:21:11):

2025-03-04

Unknown User (08:14:36): - Attachment: #3756 rigvf > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/IGVF/rigvf > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:14:38): Unknown User (08:33:56): - Attachment: #3757 rigvf > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/IGVF/rigvf > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:57:26): - Attachment: #3758 imageTCGA > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/billila/imageTCGA > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2025-03-05

Unknown User (13:29:25): Unknown User (14:25:08): - Attachment: #3759 clonality package > Hi, > the package was removed because I didn’t fix some errors that appeared in time (I fixed them in Github repository but it failed to push up). Can you please add Clonality package back to Bioconductor? > https://github.com/IOstrovnaya/Clonality > > Thanks! > Irina

Unknown User (14:25:11): Unknown User (14:28:53): Unknown User (14:29:05): - Attachment: #3760 clonality package > Hi, > the package was removed because I didn’t fix some errors that appeared in time (I fixed them in Github repository but it failed to push up). Can you please add Clonality package back to Bioconductor? > https://github.com/IOstrovnaya/Clonality > > Thanks! > Irina

Unknown User (15:44:42):

2025-03-06

Unknown User (07:08:52): - Attachment: #3761 mitology > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/CaluraLab/mitology > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (08:11:44): Unknown User (11:42:31):

2025-03-07

Unknown User (09:34:39): Unknown User (11:27:09):

2025-03-10

Unknown User (05:42:22): - Attachment: #3762 MSstatsWeightedSummary > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Vitek-Lab/MSstatsWeightedSummary/ > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [ x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:42:26): Unknown User (05:49:15): - Attachment: #3763 MSstatsWeightedSummary > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Vitek-Lab/MSstatsWeightedSummary/ > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (11:25:08): Unknown User (11:25:09): Unknown User (11:25:10): Unknown User (11:25:13): Unknown User (11:25:14): Unknown User (11:25:17):

2025-03-14

Unknown User (05:00:26): - Attachment: #3764 BenchHub > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/SydneyBioX/BenchHub > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:00:28): Unknown User (05:14:35): - Attachment: #3765 BenchHub > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/SydneyBioX/BenchHub > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:14:39): Unknown User (05:21:16): - Attachment: #3766 BenchHub > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/SydneyBioX/BenchHub > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:35:13): Unknown User (14:35:14): Unknown User (14:35:16): Unknown User (14:35:16):

2025-03-17

Unknown User (00:18:42): Unknown User (01:27:22): - Attachment: #3767 miaTime > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/microbiome/miaTime > > Confirm the following by editing each check box to ‘[x]’ > > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up.

2025-03-19

Unknown User (10:23:28): Unknown User (10:30:17):

2025-03-22

Unknown User (06:40:30): Unknown User (06:46:32): Unknown User (14:30:58): - Attachment: #3768 ToxicRToo > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/SciomeLLC/ToxicRToo > > Confirm the following by editing each check box to ‘[x]’ > > • [x ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x ] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [ x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x ] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2025-03-24

Unknown User (11:22:47): Unknown User (11:22:48): Unknown User (11:22:49):

2025-03-27

Unknown User (11:03:24): Unknown User (11:06:13): Unknown User (13:34:56): - Attachment: #3769 SignalingProfiler > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/SaccoPerfettoLab/SignalingProfiler > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:34:58): Unknown User (13:40:53): - Attachment: #3770 SignalingProfiler > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/SaccoPerfettoLab/SignalingProfiler > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (13:40:56):

2025-03-28

Unknown User (08:42:18):

2025-03-31

Unknown User (07:02:02): Unknown User (11:51:43): - Attachment: #3771 msigdbeh > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/igordot/msigdbeh > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2025-04-01

Unknown User (10:06:02): Unknown User (10:06:04): Unknown User (10:06:06): Unknown User (10:06:06): Unknown User (10:06:07): Unknown User (10:06:09): Unknown User (10:06:10):

2025-04-02

Unknown User (13:45:40): - Attachment: #3772 SpliceImpactR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/fiszbein-lab/SpliceImpactR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:51:59): - Attachment: #3773 AWAggregatorData > AWAggregatorData (https://github.com/Tan-Jiahua/AWAggregatorData) contains the metadata associated with the package AWAggregator (https://github.com/Tan-Jiahua/AWAggregator), which currently does not meet bioconductor guideline and will be adjusted for the prospective submission. > > ————————- > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Tan-Jiahua/AWAggregatorData > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (20:52:03): Unknown User (20:55:19): - Attachment: #3774 AWAggregatorData > AWAggregatorData, as an ExperimentHub package, contains the metadata associated with the package AWAggregator, which currently does not meet bioconductor guideline and will be adjusted for the prospective submission to bioconductor. > > ————————- > > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Tan-Jiahua/AWAggregatorData > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2025-04-03

Unknown User (10:32:05): - Attachment: #3775 SignalingProfiler > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/SaccoPerfettoLab/SignalingProfiler > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:50:48): - Attachment: #3776 ComBatMet > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/JmWangBio/ComBatMet > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2025-04-04

Unknown User (11:00:47): Unknown User (11:00:48): Unknown User (11:00:49): Unknown User (11:00:50): Unknown User (11:00:51): Unknown User (11:00:53): Unknown User (11:00:54):

2025-04-05

Laurent Gatto (00:59:15): > @Laurent Gatto has left the channel

2025-04-06

Unknown User (14:56:17): - Attachment: #3777 Submission Request > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/mghotbi/DspikeIn > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:56:20): Unknown User (15:13:46): - Attachment: #3778 New Package Submission: DspikeIn > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/mghotbi/DspikeIn > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x]I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2025-04-08

Unknown User (08:10:35): Unknown User (08:15:20): Unknown User (08:25:32): Unknown User (08:25:34): Unknown User (08:25:35): Unknown User (08:25:36): Unknown User (08:25:37):

2025-04-10

Unknown User (14:27:00):

2025-04-11

Unknown User (08:28:53): Unknown User (08:28:54): Unknown User (08:28:55): Unknown User (08:28:56): Unknown User (08:28:58): Unknown User (08:28:59):

2025-04-15

Unknown User (14:45:26): - Attachment: #3779 RSCUcaller > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Mordziarz/RSCUcaller > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:45:29): Unknown User (14:48:33): - Attachment: #3780 RSCUcaller > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Mordziarz/RSCUcaller > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:48:36): Unknown User (14:52:29): - Attachment: #3781 RSCUcaller > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Mordziarz/RSCUcaller > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (14:52:31): Unknown User (14:58:18): - Attachment: #3782 RSCUcaller > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Mordziarz/RSCUcaller > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2025-04-17

Unknown User (10:05:09): - Attachment: #3783 PMScanR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/prodakt/PMScanR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:05:12): Unknown User (10:11:21): - Attachment: #3784 PMScanR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/prodakt/PMScanR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:11:24): Unknown User (10:40:28): - Attachment: #3785 PMScanR > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/prodakt/PMScanR > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (19:18:16): - Attachment: #3786 igblastr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/HyrienLab/igblastr > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (19:18:18): Unknown User (19:23:28): - Attachment: #3787 igblastr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/HyrienLab/igblastr > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (19:23:30): Unknown User (20:27:25): - Attachment: #3788 igblastr > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/HyrienLab/igblastr > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2025-04-18

Unknown User (17:07:33): - Attachment: #3789 MetabolomicsPipeline package > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/datalifecycle-ua/MetabolomicsPipeline/tree/master > > Confirm the following by editing each check box to ‘[x]’ > > • [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ x] The ‘devel’ branch for new packages and features. > • [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x ] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (17:07:36): Unknown User (17:27:56): - Attachment: #3790 MetabolomicsPipeline > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > Repository: https://github.com/datalifecycle-ua/MetabolomicsPipeline/tree/master > Confirm the following by editing each check box to ‘[x]’ > > [ x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > [ x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > [ x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > [ x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > [ x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > [ x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > [ x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from mailto:noreply@bioconductor.org|<noreply@bioconductor.org|noreply@bioconductor.org> and mailto:BBS-noreply@bioconductor.org|<BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org> to allow > automatic notifications from the Bioconductor team concerning my package. > > [x ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > I am familiar with the essential aspects of Bioconductor software > management, including: > > [ x] The ‘devel’ branch for new packages and features. > [x ] The stable ‘release’ branch, made available every six > months, for bug fixes. > [x ] Bioconductor version control using Git > (optionally via GitHub). > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up.

2025-04-22

Unknown User (05:23:16): - Attachment: #3791 Add SpectriPy: integration with Mass Spectrometry libraries in Python > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/RforMassSpectrometry/SpectriPy > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org|noreply@bioconductor.org and BBS-noreply@bioconductor.org|BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2025-04-24

Unknown User (06:40:06): - Attachment: #3792 asuri > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jdelasrivas-lab/asuri > > Confirm the following by editing each check box to ‘[x]’ > > • [ X ] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [ X ] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [ X ] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [ X ] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [ X ] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [ X ] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [ X ] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org and BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [ X ] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [ X ] The ‘devel’ branch for new packages and features. > • [ X ] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [ X ] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (06:40:09): Unknown User (08:02:03): - Attachment: #3793 asuri > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/jdelasrivas-lab/asuri > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org and BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2025-04-25

Unknown User (05:00:52): - Attachment: #3794 FlexAssays > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ycli1995/FlexAssays > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org and BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (05:00:56): Unknown User (05:17:51): - Attachment: #3795 FlexAssays > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/ycli1995/FlexAssays > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org and BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2025-04-28

Unknown User (21:57:10): - Attachment: #3796 Seqinfo > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/Bioconductor/Seqinfo > > Confirm the following by editing each check box to ‘[x]’ > > • [x] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [x] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [x] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [x] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [x] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [x] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [x] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org and BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [x] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [x] The ‘devel’ branch for new packages and features. > • [x] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [x] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

2025-04-30

Unknown User (10:23:20): - Attachment: #3797 CrossExpression > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/gillislab/CrossExpression > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org and BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:23:35): Unknown User (10:25:22): - Attachment: #3798 CrossExpression > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/gillislab/CrossExpression > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org and BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (10:25:25): Unknown User (10:27:46): Unknown User (10:35:12): Unknown User (10:36:24): - Attachment: #3799 CrossExpression > Update the following URL to point to the GitHub repository of > the package you wish to submit to Bioconductor > > • Repository: https://github.com/gillislab/CrossExpression > > Confirm the following by editing each check box to ‘[x]’ > > • [X] I understand that by submitting my package to Bioconductor, > the package source and all review commentary are visible to the > general public. > > • [X] I have read the Bioconductor Package Submission > instructions. My package is consistent with the Bioconductor > Package Guidelines. > > • [X] I understand Bioconductor <https://bioconductor.org/developers/package-submission/#naming|Package Naming Policy> and acknowledge > Bioconductor may retain use of package name. > > • [X] I understand that a minimum requirement for package acceptance > is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS. > Passing these checks does not result in automatic acceptance. The > package will then undergo a formal review and recommendations for > acceptance regarding other Bioconductor standards will be addressed. > > • [X] My package addresses statistical or bioinformatic issues related > to the analysis and comprehension of high throughput genomic data. > > • [X] I am committed to the long-term maintenance of my package. This > includes monitoring the support site for issues that users may > have, subscribing to the bioc-devel mailing list to stay aware > of developments in the Bioconductor community, responding promptly > to requests for updates from the Core team in response to changes in > R or underlying software. > > • [X] I understand it is my responsibility to maintain a valid, active > maintainer email in the DESCRIPTION of my package. This email should allow > emails from noreply@bioconductor.org and BBS-noreply@bioconductor.org to allow > automatic notifications from the Bioconductor team concerning my package. > > • [X] I am familiar with the Bioconductor code of conduct and > agree to abide by it. > > > I am familiar with the essential aspects of Bioconductor software > management, including: > > • [X] The ‘devel’ branch for new packages and features. > • [X] The stable ‘release’ branch, made available every six > months, for bug fixes. > • [X] Bioconductor version control using Git > (optionally via GitHub). > > For questions/help about the submission process, including questions about > the output of the automatic reports generated by the SPB (Single Package > Builder), please use the #package-submission channel of our Community Slack. > Follow the link on the home page of the Bioconductor website to sign up. > > [1]: https://contributions.bioconductor.org/ > [2]: https://bioconductor.org/developers/package-submission/ > [3]: https://support.bioconductor.org > [4]: https://stat.ethz.ch/mailman/listinfo/bioc-devel > [5]: http://bioconductor.org/developers/how-to/git/ > [6]: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/ > [7]: https://bioconductor.org/about/code-of-conduct/ > [8]: https://bioconductor.org/ > [9]: https://bioconductor.org/developers/package-submission/#naming

Unknown User (16:06:29): Unknown User (16:46:30): Unknown User (16:46:31):